Issue metadata
Sign in to add a comment
|
HTTP/2 fails on receiving interim responses
Reported by
stefan.e...@gmail.com,
Nov 30 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14 Example URL: Steps to reproduce the problem: 1. Install a Apache httpd from trunk or 2.4.x branch (or take 2.4.24 when it is available) 2. Enable HTTP/2 protocol (see howto) 3. Add directive 'H2PushResource <path>' to your configuratio 4. Access such a url with chrome, observe path being PUSHed 5. Add directive 'H2EarlyHints on', reload the server 6. Reload the page and observe a spdy protocol error What is the expected behavior? Chrome should ignore an http response in the range 100-199 which it does not understand. What went wrong? Chrome aborted the connection and the page did not load. Did this work before? No Chrome version: 54.0.2840.98 (Offizieller Build) (64-Bit) Channel: stable OS Version: OS X 10.12.1 Flash Version: 23.0.0.207 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by b...@chromium.org
, Nov 30 2016Status: Duplicate (was: Unconfirmed)