Closed rnapier closed 10 years ago
I'm afraid I'm very busy at the moment and won't be free to do any development for several days. I'll get on this as soon as I can, though.
Thanks. I'm currently pursuing other approaches that don't require httptest.
On Wed, May 28, 2014 at 12:23 PM, Jamie Hall notifications@github.comwrote:
I'm afraid I'm very busy at the moment and won't be free to do any development for several days. I'll get on this as soon as I can, though.
— Reply to this email directly or view it on GitHubhttps://github.com/SlyMarbo/spdy/issues/49#issuecomment-44430675 .
Rob Napier -- Software and Security Consulting Cocoaphony blog -- http://robnapier.net/blog iOS Programming Pushing the Limits -- http://robnapier.net/book
I've been trying to create some unit tests so I can more easily reproduce the race conditions. I'm having a bit of trouble getting spdy to use SPDY when in an httptest server.
This test case works, but it runs over HTTPS. I haven't been able to convince it to run under SPDY (so I'm not testing the code I want to test).
I tried adding
NextProtos: []string{"spdy/3.1"}
to thetls.Config
, which seems part of the answer, but I then get "spdy3_conn.go:1018: Error: Encountered error: "Error: Field \"flags\" recieved invalid data 47, expecting 1." (*spdy.invalidField)". Adding the same thing to server doesn't improve things.It's failing at transport.go:227:
At this point,
state.NegotiatedProtocol
isspdy/3.1
, butNegotiatedProtocolIsMutual
isfalse
.Given spdy's design, this feels like it should be pretty straightforward, so I'm not sure if I'm missing something simple or there's a bug.
I based all of this on the http package's tests.