Oh, sorry.
It's clear that the upstream is sending 413 errors, not the nginx himself.
Should read the log more carefully.
Sorry again.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,285564,285565#msg-285565
___
nginx mailing list
Hello,
I was getting the bunch of 413 statuses in the access log along with getting
explicit error messages about client (logstash in my case, seems like it was
trying to send bodies around 100 megabytes) trying to post body larger than
the client_max_body_size. After I raised this setting to
Hello,
I did't find the answer in documentation, but am I right, assuming from my
observation, that when the proxy_cache is enabled for a location, and the
client requests the file that isn't in the cache yet, nginx starts
transmitting this file only after it's fully received from the upstream ?
Oh, solved. Upstreams do respond with 500.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,269577,269584#msg-269584
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
(yup, it's still the author of the original post, but my other browser just
remembers another set of credentials).
If I increase verbosity of the error_log, I'm seeing additional messages in
log, like
upstream server temporarily disabled while reading response header from
but this message
Is there someone besides Captain Evidence who knows the answer ? This is
actually the problem of the modern internet: half of the decent questions is
flooded out by people, who not only think they know the answer, but are
arrogant enough to insist it, and from the point of an outer observer the
What is the scope of the upstream member liveness: is it per upstream group,
or per vhost ?
If the question is unclear, consider I have 3 nginx - one balancer and two
backends, and the following config part on the nginx balancer:
upstream backends {
server 192.168.0.1;
server
Hi.
I'm trying to get nginx 1.6.2 to authenticate users using their client
certificates.
I'm using this configuration (besides usual SSL settings, which are proved
to work):
ssl_stapling on;
ssl_client_certificate /etc/nginx/certs/trusted.pem;
ssl_verify_client optional_no_ca;
trusted.pem