On 4/9/12 11:04 AM, Philip wrote:
Hi,
I have just started testing trafficserver in production but for some
reason my error log is full of such lines:
20120409.18h42m47s RESPONSE: sent 41.249.21.105 <tel:41.249.21.105> status
400 (Invalid HTTP Request) for '/'
20120409.18h42m48s RESPONSE: sent 88.231.146.188 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m49s RESPONSE: sent 119.93.197.215 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m50s RESPONSE: sent 94.120.152.153 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m50s RESPONSE: sent 35.32.231.34 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m52s RESPONSE: sent 75.147.253.45 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m52s RESPONSE: sent 58.106.6.105 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m52s RESPONSE: sent 80.216.110.194 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m53s RESPONSE: sent 190.82.40.192 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m53s RESPONSE: sent 213.151.57.111 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m56s RESPONSE: sent 82.38.126.80 status 400 (Invalid HTTP
Request) for '/'
20120409.18h42m58s RESPONSE: sent 189.153.63.57 status 400 (Invalid HTTP
Request) for '/'
A *wild* guess is that these are clients disconnecting. I changed this error
message on trunk to reflect that the client has disconnected instead of
giving this error (the old code will try to "parse" the empty request line,
and therefore gives that error). The new version (e.g. 3.1.3 or trunk) will
detect the client disconnecting, and not try to parse the empty request.
-- Leif
