Skip To Main Content | Accessibility

Begin Main Content
Index
No registered users in community xowiki
in last 10 minutes

Weblog Page

Showing 1 - 4 of 4 Postings (summary)

A ballpark situation

Created by Iuri Sampaio, last modified by Iuri Sampaio 02 Jul 2019, at 12:29 AM

A ballpark situation is when you are in the code and have now ideia where the error is. So, write in as much as FLAGs as possible, then wehere is stops, that's the piece you are loking for,

Nginx Proxy: upstream sent too big header while reading response header from upstream

Created by Iuri Sampaio, last modified by Iuri Sampaio 30 Jun 2019, at 02:39 PM

If you're running an Nginx proxy configuration, you can run into the following error in your logs.

$ tail -f error.log
[error] 19896#0: upstream sent too big header while reading response header from upstream,
client: 10.5.120.6,
server: host.tld,
request: "GET /path/to/file.php HTTP/1.1",
upstream: "",
host: "host.tld"

[error] 19899#0: upstream sent too big header while reading response header from upstream,
client: 10.5.120.6,
server: host.tld,
request: "GET /path/to/file.php HTTP/1.1",
upstream: "",
host: "host.tld"

In your Nginx proxy configuration, you probably have something very similar to this:

server {
listen 80;
server_name host.tld;

location / {
proxy_pass http://upstream;
...
}
}

To resolve this issue, increase the proxy buffers that nginx uses. Before nginx sends a response back to your visitor, it will cache the request it had to make from its upstream. However, there are limited buffers available to buffer such a response. If the HTTP headers contain more info than anticipated, those proxy buffers can get saturated and nginx will drop the request with the "upstream sent too big header while reading response header from upstream" error in your logs.

To resolve it, add the proxy_buffer_size configurations to your location block.

server {
listen 80;
server_name host.tld;

location / {
proxy_pass http://upstream;
...

proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
}
}

That change increases Nginx's proxy buffer from the default 4KB to 128KB, usually big enough to cache any backend response without posing a risk to your server. After all, that server now has to assign more memory to buffer each backend response.

'AWSHTTPSConnection' object has no attribute 'ssl_context'

Created by Iuri Sampaio, last modified by Iuri Sampaio 15 Jun 2019, at 10:29 PM

https://stackoverflow.com/questions/45821085/awshttpsconnection-object-has-no-attribute-ssl-context

Index Page

Created by , last modified by Guest 20 Mar 2019, at 04:59 AM

This is the default start page of XoWiki. You can edit this page and save it to provide a personalized look of the XoWiki instance. You can as well provide a different index page through configuration. You can also view the contents of the Wiki in a weblog style. For more details, consult the XoWiki documentation .

A user can define notifications for the whole XoWiki instance (by clicking on the notifications button in the menu bar or for categories (by clicking on the letter symbol next to the category entries at the bottom of the page)

Recently Changed Pages
Last ModifiedTitle
2019-07-02 00:29:20A ballpark situation
2019-06-30 14:39:14Nginx Proxy: upstream sent too big header while reading response header from upstream
2019-06-15 22:29:53'AWSHTTPSConnection' object has no attribute 'ssl_context'
2019-03-20 16:00:05Weblog
2019-03-20 04:59:48Index Page
2019-03-20 02:28:50Weblog