Recently had an issue develop. A page made long ago had a
"Content/Type" instead of Content-type. It was working until recently
and then started showing 502 errors. Issue resolved by user fixing their
page to have "Content-Type".
Was looking at the rfc and seems this could be treated as an
invalid/non-existant Content-type:
*************RFC2045*****************
Default RFC 822 messages without a MIME Content-Type header are taken
by this protocol to be plain text in the US-ASCII character set,
which can be explicitly specified as:
Content-type: text/plain; charset=us-ascii
This default is assumed if no Content-Type header field is specified.
It is also recommend that this default be assumed when a
syntactically invalid Content-Type header field is encountered. In
the presence of a MIME-Version header field and the absence of any
Content-Type header field,....
***********end of RFC2045 quote***********
Or is it that stray slashes in the header fields will cause these
failures? Not necessarily a haproxy bug but looks like older versions
of haproxy may have allowed for overlooking these slash issues.
--
Thank You
David Blomberg
