ERR_SPDY_PROTOCOL_ERROR
Reported by
jimmy.de...@powerdms.com,
Apr 24 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Steps to reproduce the problem: 1. Update to newest version of Chrome 2. Go to powerdms.com 3. What is the expected behavior? I can view the marketing site for my company. What went wrong? I am getting ERR_SPDY_PROTOCOL_ERROR and cannot view the entire site. Chrome is 33% of our user base. Did this work before? Yes The version right before this new version. I dont know the numbver Chrome version: 58.0.3029.81 Channel: stable OS Version: OS X 10.12.4 Flash Version: I cannot find anything about what causes this issue to know if something with my site is incompatible that I can fix.
,
Apr 24 2017
This shouldn't be a release blocker. This is likely that one of the response headers sent by the website is not RFC-compliant. I can check which one.
,
Apr 24 2017
There is an invalid header-value pair at the end of response headers. This looks like a server bug. jimmy.dempsey@powerdms.com, could you check where the the last response header comes from? [link] [<https://www.powerdms.com/wp-json/>; rel="https://api.w.org/"] [link] [<https://www.powerdms.com/>; rel=shortlink] [cache-control] [max-age=2592000] [expires] [Wed, 24 May 2017 21:28:10 GMT] [vary] [Accept-Encoding] [content-encoding] [gzip] [:status] [200] [date] [Mon, 24 Apr 2017 21:28:15 GMT] [content-type] [text/html; charset=UTF-8] [content-length] [11316] [server] [Apache] [ ] [] <- an invalid header name. Looks like it's a whitespace of some sort.
,
Apr 25 2017
We were able to resolve this on our side. The blank/whitespace header field names and values were caused a bug in the "w3 Total Cache" WordPress plugin when Memcached page caching was enabled. Our AWS application load balancer (ALB) accepts and terminates HTTP2 connections. HTTP2 support is not configurable on the AWS ALB and is always enabled. The newest version of Chrome connects to the ALB with HTTP2, but received invalid headers from WordPress. The ALB does not seem to modify or inspect response headers from backend instances. This issue was resolved by disabling page caching in w3 Total Cache and filing a bug report with the author.
,
Apr 28 2017
Thanks jimmy.dempsey@powerdms.com. I will close this issue now. I filed Issue 714809 to add NetLogs so you can discover any invalid headers next time in chrome://net-internals. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ligim...@chromium.org
, Apr 24 2017Components: Internals>Network Enterprise
Labels: -Pri-2 hasbisect-per-revision ReleaseBlock-Stable Prestable-58.0.3029.81 Needs-Triage-M58 M-58 OS-Android OS-Linux OS-Windows Pri-1
Owner: xunji...@chromium.org
Status: Assigned (was: Unconfirmed)