Maxim, thank you for reply!
Some additional question here:
1. If we will remove 'timeout' will Nginx send traffic to the next upstream
on 502 error?
2. More general question related the the Q.1. When Nginx interpret reply as
502 - on timeout, if yes - on which one? We have a lot of timeouts define
Hello,
We have an Nginx where we configured
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_next_upstream
in Nginx main config file at http level.
We don't want to send traffic to the next upstream on 504:
proxy_next_upstreamerror timeout http_502 http_503 non_idempotent;
Hello Francis,
It seems that your solution working as expected and I have started to test
it. Also, have some questions here:
1. "~*" to be "~^"
The first one looks like Nginx regexp we can use for locations, but the
second one not (^~):
https://www.digitalocean.com/community/tutorials/understand
Hello,
We have a case when we should permit different methods on the same location
but different requests.
For location /test we should permit only POST, for /test?doc we should
permit only GET methods.
Our config example:
location /test {
error_page 403 =405 /custom-error;
limi
Maxim,
Different locations solved the issue.
Thank you for the help!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,286421,286423#msg-286423
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
We use Nginx map module to sent traffic to different upstreams based on the
HTTP header:
map $http_flow $flow_upstream {
default "http://flow-dev";;
prod"http://flow-prod";;
test"http://flow-test";;
dev "http://flow-dev";;
}
location / {
proxy_read_timeout 5s;
Francis,
Basically, the issue was with the 'proxy_set_header' directives. In such
cases, when we define at least one in the location, we should also define
all the rests headers.
>From your reply, I understand that with the
'proxy_read_timeout/proxy_send_timeout' we should not have such situation
Hello,
We recently made some order in our configuration to make it cleaner and
readable.
We have moved all reverse proxy related parameters on the HTTP level from
the vhosts locations:
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X
