| Bug ID |
10566
|
| Summary |
The spdy dissector couldn't dissecting packet correctly
|
| Product |
Wireshark
|
| Version |
1.12.1
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Wireshark Version: 1.12.1 (v1.12.1-0-g01b65bf from master-1.12)
Platform Version: Windows 7
Chrome Version: 38.0.2125.101 m
Apache Version: Apache/2.2.15 (Unix)
mod-spdy Version: Most currently
--
Step to reproduce:
1. Force apache server to use spdy over non-ssl connection:
Edit the configuration file (for example):
SpdyDebugUseSpdyForNonSslConnections 3
2. Start chrome with spdy by default:
chrome --use-spdy=no-ssl
3. Open wireshark with some capture filter like "port 80" and access any
content from the Webserver.
4. Manually select spdy dissector over transport layer via menu Analyze ->
Decode As...
Phenomenon:
The control frames are decoded as non-control frame. Specifically, the control
bit cannot be dissected correctly.
Extra information:
When compared the spdy dissector contributed by google itself, it works
correctly. And it can give more indicative information in the info colume in
the GUI.
You are receiving this mail because:
- You are watching all bug changes.