Well, yes, spaces are illegal, which is why apache returned a 400
error on those requests. The log is simply reporting the request line
as received by the client (with quote-escaping).
In my view, the parsing rules are relatively clear. Fields in the logs
(in common log format and its derivatives) are space or double-quote
separated, depending on whether the field itself could contain a
space. Where double-quotes are contained in a quoted field, they are
escaped with a back-slash.
A log parser then needs to understand the quote-escaping in order to
extract the fields. If your log-parser doesn't understand that, it
won't work.
The other problem here is that, within the request line field, the
parser is probably having a hard time differentiating between the URI
and the protocol string. But that is to be expected, since this is a
bad request. There is no way for either the server or the log parser
to correctly parse it. How a stats program wants to handle requests
like that is a judgment call.
Thanks.
Am I correct in that this is a bug in the google analytics javascript,
and they are sending in a bad request?
--
Scott
[EMAIL PROTECTED]
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
