search

patricmutwiri / mod-spdy

Automatically exported from code.google.com/p/mod-spdy
0 stars 0 forks source link

session corruption issue #18

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I see the following in the logs:

[Wed Dec 21 20:22:34 2011] [warn] [25111:25154:WARNING:spdy_connection.cc(239)] 
  bad stream id, aborting stream
[Wed Dec 21 20:22:34 2011] [error] 
[25111:25118:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 83
[Wed Dec 21 20:22:34 2011] [error] 
[25111:25119:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 85
[Wed Dec 21 20:22:34 2011] [error] 
[25111:25120:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 87
[Wed Dec 21 20:22:35 2011] [error] 
[25111:25121:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 89
[Wed Dec 21 20:22:38 2011] [error] 
[25111:25122:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 91
[Wed Dec 21 20:22:45 2011] [error] 
[25111:25118:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 93
[Wed Dec 21 20:22:47 2011] [error] 
[25111:25119:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 95
[Wed Dec 21 20:23:39 2011] [error] 
[25111:25120:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 97
[Wed Dec 21 20:23:40 2011] [error] 
[25111:25121:ERROR:spdy_to_http_filter.cc(339)] Invalid SYN_STREAM header block 
in stream 99

on the client side, once this happens, I am totally hosed. I'm guessing the 
decompression context is out of sync. There is a TODO(mdsteele) in the code to 
decompress all frames even if we don't care about them. My hunch is that fixing 
that TODO will fix this issue.

Original issue reported on code.google.com by bmcqu...@google.com on 21 Dec 2011 at 8:51

GoogleCodeExporter commented 8 years ago 
I've made a change in r214 that I hope will fix this.  Can you sync and give it 
a try?

Original comment by mdste...@google.com on 22 Dec 2011 at 3:52

GoogleCodeExporter commented 8 years ago 
I believe this has been fixed.

Original comment by mdste...@google.com on 27 Jan 2012 at 11:23