[
https://issues.apache.org/jira/browse/TS-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-1056:
------------------------------
Attachment: HttpSM.diff
> Lost UA connections can show up as "400 ERR_INVALID_REQ" in logs
> ----------------------------------------------------------------
>
> Key: TS-1056
> URL: https://issues.apache.org/jira/browse/TS-1056
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 3.1.2
>
> Attachments: HttpSM.diff
>
>
> So, it seems that with Firefox (it's the only one I've been able to reproduce
> this with), we can end up getting a bunch of errors like
> {code}
> 1324075013.826 0 216.239.45.4 ERR_INVALID_REQ/400 217 - / - NONE/- text/html -
> {code}
> Tracking this down, it seems the HTTP SM is getting a VC_EVENT_EOS (stream
> closed) in state_read_client_request_header(). However, there is nothing in
> the request_header (zero bytes), so when it tries to parse the (empty)
> request header, it looks like a request error.
> I'm not certain, yet at least, under what conditions we get this event (I'm
> fairly certain that Firefox is somehow closing down the connection in some
> weird state to us?). So, I'm suggesting we at least deal with this situation
> earlier (before trying to parse the headers), which will instead cause an
> "UNKNOWN_ERROR" (since we have no request nor response code. Suggested
> changes attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
