Closed arashpayan closed 9 years ago
This is a very odd issue. spdy
detects which version has been negotiated by looking at the NPN protocol string, which normally takes the form spdy/x
. In this instance, the negotiated protocol is the empty string, which tends to indicate HTTP
. When I last checked, net/http
treats this as normal and continues with the HTTP processing. Let me take another look at net/http
and see whether something has changed.
Ah, I see what's happened; a silly oversight on my part. Fix on its way.
Brilliant. Thank you so much! :smiley:
No problem :)
First off, thank you for the terrific library. I was able to enable SPDY support in my web service in just a few minutes with it. :smile:
I see inside
client.go
'sinit()
http.DefaultClient
to enable SPDY support, but when I make calls to api.linode.com I getGet https://api.linode.com: Error: Unsupported negotiated protocol "".
This gist contains sample code that reproduces the issue. https://gist.github.com/arashpayan/3927d6aae5e8e01aa43d
In the meantime, I just replace the
http.DefaultClient
at the beginning of my app with one without SPDY support.