No CORS Workaround - SSL Proxy
eswenson at intertrust.com
Tue Jul 1 17:58:33 UTC 2014
On 6/22/14, 7:32 AM, "Maxim Dounin" <mdounin at mdounin.ru> wrote:
>If there is nothing in error logs, and you are getting 502 errors,
>then there are two options:
>1. The 502 errors are returned by your backend, not generated by
>2. You did something wrong while configuring error logs and/or you
> are looking into a wrong log.
>In this particular case, I would suggest the latter.
I¹ve verified that my error log are configured fine ‹ I do get errors
reported in my configured error log ‹ but nothing at the time that nginx
returns 502 errors to the client.
I¹ve checked the upstream server¹s logs, even when configured with debug
logging, and never see any requests making it to the upstream server when
nginx returns a 502 to the client.
If the issue were with the upstream server, why is it that simply
restarting nginx causes everything to proceed normally. I never have to
touch the upstream server (which, by the way is serving other requests
successfully from other proxies at the same time as the nginx proxy that
returns 502s is doing do.
More information about the nginx