New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERR_SPDY_PROTOCOL_ERROR #151
Comments
Did you enable SPDY/4 (aka HTTP/2 draft) in Chrome 40? Then it must be disabled or configure nghttpx with --npn-list=spdy/3.1 so that it only negotiates spdy/3.1. |
I see ERR_SPDY_PROTOCOL_ERROR in Chrome 42 as well but with Enabling or disabling SPDY/4 in Chrome does not have any effect on this. I compiled Firefox 37 however doesn't seem to have a problem with this. It reports X-Firefox-Spdy h2 so I digged a little bit and the problem seems to raise with the usage of When I run |
Your description suggests that Chrome does not support HTTP/2 trailer fields. Did you raise an issue about this in Chromium bug tracker? |
@tatsuhiro-t Not yet. Seems like the right place though (still very very new to this). |
Yeah, trailer fields are not so popular in HTTP/1.1 since it requires chunked encoding and not all implementation supports trailer. I don't see how it is used in practice. |
I raised https://code.google.com/p/chromium/issues/detail?id=481033 - hope this describes it well. |
Thanks! Let's wait and see.. |
@Bekoli Same problem in Chrome 41. You can just set 'npn-list=spdy/3.1' in nghttpx.conf to avoid it. @tatsuhiro-t And in FireFox 37, there is another problem. When access to a website via ssl proxy (e.g. nghttpx), FireFox show 'sec_error_unknown_issuer' error, because it got certificate issues to proxy's domain. |
@tatsuhiro-t Correction, FireFox shows 'sec_error_unknown_issuer' just because I did not use an right cert contains root CA. My apologies for the oversight. |
@cnrat I got this error with I see I wrote the command wrong above. Going to correct this. |
@Bekoli I got a reply 3 days ago in issue 433784 https://code.google.com/p/chromium/issues/detail?id=433784, it is said this bug will be fixed soon. |
@cnrat Oh, so this is really the same bug? In that case is my ticket a duplicate. Thanks for posting. I'll watch this as well. |
Probably they are different bugs. The original bug reported here is due to prohibited header field sent by chrome. While the bug @Bekoli reported is chrome drops connection if it sees trailer field. |
I got |
@catatnight will you please run telnet command to prove the connectivity? |
@cnrat Yes, connectivity on both sides is surely OK. |
@catatnight Please make sure that you have built nghttp2 with libspdylay. nghttpx --npn-list can accept anything, without considering libspdylay support. |
@catatnight if you set nothing with npn-list witch means it will use 'h2,h2-16,h2-14,spdy/3.1,http/1.1' as default. Due to the bug mentioned above, Chrome 43 still can not work with h2 protocol(also the same Chrome Canary 45). |
@tatsuhiro-t Thanks. Problem solved. |
@tatsuhiro-t looks like https://code.google.com/p/chromium/issues/detail?id=481033 was closed a month ago by https://code.google.com/p/chromium/issues/detail?id=433784 was closed as well (you raised this so I guess you know). I'd say this can be closed as well now :) |
Thank you for heads up. Let's close this issue. |
Confirmed. Chrome Canary 47 now working good with H2. |
There are many ways to fix via below points
You can follow this guide to fix using this method too. |
Well, Identified the issue deeply and it occurs frequently in Internet Browsers due to some uncommon reasons. I have listed down all the possible solutions and 99% your issue is going to resolve from one of the solution. Try them one by one and do reply which solution solved your issue. Solutions Page: How to Solve Google Chrome’s Error “ERR_SPDY_PROTOCOL_ERROR” |
Hi, |
As you can see, this is the error: http://i.imgur.com/bZGOEiQ.png
Running on SPDY reverse proxy on Chrome 40, Windows XP. @tatsuhiro-t, any idea on why this happens?
The text was updated successfully, but these errors were encountered: