Ok, I figured it out. Seems that several years ago someone at my day job
did a custom errorfile in haproxy which returns a 503 error whenever
haproxy intends to return a 403 error. It was forgotten and went unnoticed
until now. Now we have to figure out if its a cut and paste error or if
there was
It sounds like this is not as straight forward as I had hoped, I'll do like
Francis Daly said and put together a test case - I'll get some packet
captures to see what exactly is being sent between all the components.
On Fri, Apr 15, 2016 at 4:49 PM, Валентин Бартенев wrote:
> On Thursday 14 Apr
On Thursday 14 April 2016 22:45:36 CJ Ess wrote:
> In my environment I have Nginx terminating connections, then sending them
> to an HAProxy upstream. We've noticed that whenever HAProxy emts a 403
> error (Forbidden, in response to our ACL rules), NGINX reports a 503 result
> (service unavailable)
On Thu, Apr 14, 2016 at 10:45:36PM -0400, CJ Ess wrote:
Hi there,
> In my environment I have Nginx terminating connections, then sending them
> to an HAProxy upstream. We've noticed that whenever HAProxy emts a 403
> error (Forbidden, in response to our ACL rules), NGINX reports a 503 result
> (s
In my environment I have Nginx terminating connections, then sending them
to an HAProxy upstream. We've noticed that whenever HAProxy emts a 403
error (Forbidden, in response to our ACL rules), NGINX reports a 503 result
(service unavailable) and I believe is logging an "upstream prematurely
closed
