> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/troubleshooting/waf-gateway-virtual-machine/nginx-error-upstream-sent-too-big-header-while-reading-response-header-from-upstream.md).

# NGINX Error: Upstream Sent Too Big Header While Reading Response Header from Upstream

NGINX is not able to read the header that is sent from the upstream as it is bigger than the configured size and the request is failing. In the NGINX error log (locating in: /var/log/nano\_agent/rpmanager/nginx\_log/error.log): "...\*1435367 upstream sent too big header while reading response header from upstream ..."

The configured buffer that caches the responses is too small.

**WHAT TO DO?**

1. Open the Infinity Portal
2. Click on **Cloud** tab → **Assets**
3. Navigate to the relevant asset and click on it.
4. Click on **Advanced...** (Under the certificate section), and click on **Additional Settings**\
   ![](/files/H5mFpaTMNokhoA1cUr9W)
5. Mark V on the **Additional Location Block** Instruction checkbox and upload a .txt file with these lines in it:\
   `proxy_buffer_size          128k;`\
   `proxy_buffers              4 256k;`\
   `proxy_busy_buffers_size    256k;`\
   \
   ![](/files/S92cLmDMQHcYgftyCHq2)
6. Click **OK**.
7. **Enforce** the policy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://waf-doc.inext.checkpoint.com/troubleshooting/waf-gateway-virtual-machine/nginx-error-upstream-sent-too-big-header-while-reading-response-header-from-upstream.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.