thanks Igor very insightful :)
I guess tricky issue is for SEO forum closure having SEO friendly http
status code alternative to 503 ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,270850,270854#msg-270854
___
nginx mailing list
nginx@ngi
The behaviour of a single and multiple upstreams is changed due to
'http_503' option of 'fastcgi_next_upstream' .
When a request comes to nginx, nginx forwards it to an upstream, tries
to get a response, gets 503. http 503 is set to be a failed response
(with proxy_next_upstream directive). So
Was wondering if anyone could shed some light on this issue I am
experiencing only with multiple php-fpm pool setups but not with single
php-fpm pool. The issue is when a forum software like Xenforo or Invision
board uses their native forum close option to turn off the forums for guests
but still a
