Actions
Bug #170
closedlighttpd shouldn't print unprintable characters to error log
Status:
Invalid
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:
Description
2005-06-18 22:20:20: (request.c.510) overlong request line -> 400 2005-06-18 22:20:20: (request.c.512) request-header: ¼égH ` égø¾~ðégàzz(iL}äégxìg@!!ø¾~h¡t$lal, He )i%8<øä@sans-se8¾~¾~øȾ~ø¾~àÈ´4ég( ø H @ 4 %±LHGET /i?region=104&name=3693 HTTP/1.1 User-Agent: Opera/7.54 (Windows NT 5.1; U) [ru] Host: [cut] Accept: text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1 Accept-Language: en Accept-Charset: windows-1252, utf-8, utf-16, iso-8859-1;q=0.6, *;q=0.1 Accept-Encoding: deflate, gzip, x-gzip, identity, *;q=0 Referer: [cut] Cookie: [cut] Cookie2: $Version=1 Connection: Keep-Alive, TE TE: deflate, gzip, chunked, identity, trailers
-- Elan Ruusamäe <glen
Updated by stbuehler over 16 years ago
- Status changed from New to Fixed
- Resolution set to invalid
nobody forces you to turn on log-request-on-error.
Actions
Also available in: Atom