> So maybe I should enable this...
After enabling WARN, I'm getting stuff like:
2013/10/15 09:54:27| WARNING: found whitespace in HTTP header name {Cache Control: no-cache}
2013/10/15 09:54:27| WARNING: found whitespace in HTTP header name {Cache Control: no-store}
2013/10/15 09:54:27| WARNING: found whitespace in HTTP header name {Cache Control: must-revalidate}
2013/10/15 09:54:27| WARNING: found whitespace in HTTP header name {Cache Control: max-age=0}
and
2013/10/15 01:15:45| WARNING: unparseable HTTP header field {: }
2013/10/15 01:18:19| WARNING: unparseable HTTP header field {: }
and
2013/10/15 07:47:15| WARNING: unparseable HTTP header field {::RETURN::NOTAVAILABLE::/mibe/404/ in the ActVersionMode}
2013/10/15 09:35:11| WARNING: found whitespace in HTTP header name {JSESSIONID=AC28912A7C462A9752761882F4A31BCE; Path=/cae: }
2013/10/15 09:35:11| WARNING: found whitespace in HTTP header name {JSESSIONID=AC28912A7C462A9752761882F4A31BCE; Path=/cae: }
Just for the fun of it: How do I correlate these warning to actual
requests done by clients?
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebrandt@xxxxxxxxxx Campus Benjamin Franklin
http://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
