Hi

Using HAproxy 1.4.8.

One of our applications generates an HTTP 302 redirect with a really
long Location. In one instance I've looked at, the Location: header is
8,175 bytes. If we bypass HAproxy, the browser happily goes to the
returned URL, if we instead go via HAproxy, the 302 is turned into a
"502 Bad Gateway -  The server returned an invalid or incomplete
response."

I couldn't find any reference stating that there is a limit to the
length of the Location: header, but that's all that seems odd about
this. In other cases, the same application generates a 302 with a
shorter Location: header which HAproxy passes on to the client, no
problem.

Can anyone shed some light on what the problem is here?

Thanks,
Graeme.

Reply via email to