Forum Discussion
wfaulk_98141
Altostratus
Oct 27, 2014I'm seeing the same problem, but my Wireshark does support SPDY. The transaction looks like this:
- Client opens TCP connection
- SSL handshaking
- Server sends SPDY: SETTINGS, MAX_CONCURRENT_STREAMS: 10, INITIAL_WINDOW_SIZE: 32768
- Client closes TCP connection
- Client opens TCP connection
- SSL handshaking
- Server sends SPDY: SETTINGS, MAX_CONCURRENT_STREAMS: 10, INITIAL_WINDOW_SIZE: 32768
- Client sends SPDY: SETTINGS, MAX_CONCURRENT_STREAMS: 1000, INITIAL_WINDOW_SIZE: 10485760
- Server initiates closure of TCP connection
- Client sends SPDY: SYN_STREAM (FIN), Stream: 1, Request: GET https://xx.xx.xx.xx/ HTTP/1.1
- Client completes TCP close
Comparing that to a successful transaction (from Chrome on a Mac) shows no differences in SPDY up until the F5 closes the connection from the Android device and replies to the stream request from Chrome.
There are some minor differences in the SSL handshaking, but they both seem to complete without error.