Hi Matthieu,
On Mon, Dec 05, 2016 at 11:35:54AM +0100, Matthieu Guegan wrote:
> This extra `\r\n` seems to be harmless with another HAproxy instance in front
> of it (sanitizing) or when using a browser. But we confirm that the
> CloudFlare NGINX implementation is not able to handle this. It seems that
> both 'Content-length: 0' and extra carriage return broke RFC (to be
> confirmed).
This extra CRLF marks the end of headers and everything which follows is
a body, so nginx does the right thing by not seeing it since it's a bug.
I've merged the fix now. I can confirm that the very first commit that
brought this feature was already bogus (commit 0140f25 ("[MINOR] redirect:
add support for "set-cookie" and "clear-cookie"", merged in 1.3.16-rc1)!
thanks!
Willy
