I've found the error in the backend server, not in Nginx.
We can close this thread, apologies!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241447,241477#msg-241477
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/lis
I've upgraded the nginx version 1.24 to 1.4.2, but this behavior still
happens.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241447,241459#msg-241459
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
Currently, we use Nginx as a reverse proxy without cache. Last monday we've
rolled out a new version of PHP application which has appeared a several 502
errors.
First of all, i've applied the workaround explained in thread
http://forum.nginx.org/read.php?2,188352 . The number of 502 have fa