[
https://issues.apache.org/jira/browse/TS-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163834#comment-14163834
]
Sudheer Vinukonda commented on TS-3121:
---------------------------------------
Note that, the commit here doesn't address the root cause yet. From what I can
see so far, the issue is mainly due to the below code in FetchSM.cc. When
there's some error in the Http layer (say, an active_timeout), HTTP layer shuts
down (which is the PluginVC's passive side). The active side then tries to send
an error message to SPDY via FetchSM, but, the below code could blindly send
TS_FETCH_EVENT_EXT_HEAD_DONE, which confuses SPDY to treat this as a valid
response.
void
FetchSM::InvokePluginExt(int fetch_event)
{
//..
if (!has_sent_header) {
contp->handleEvent(TS_FETCH_EVENT_EXT_HEAD_DONE, this);
has_sent_header = true;
}
//..
..
}
> Seeing garbage Spdy responses sometimes
> ---------------------------------------
>
> Key: TS-3121
> URL: https://issues.apache.org/jira/browse/TS-3121
> Project: Traffic Server
> Issue Type: Bug
> Components: SPDY
> Affects Versions: 5.0.1
> Reporter: Sudheer Vinukonda
> Assignee: Sudheer Vinukonda
> Fix For: 5.2.0
>
>
> Seeing some HTTP/0.9 version garbage responses with status=0 from SPDY
> sometimes. In some error cases, when http layer cleans up itself and sends a
> FETCH ERROR to the SPDY layer and SPDY layer seems to build a SYN_REPLY with
> garbage HTTP headers. Adding a simple protection to prevent this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
