Issue metadata
Sign in to add a comment
|
Chrome does not handle 408 response in HTTP2
Reported by
tamilara...@gmail.com,
Feb 22 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Enable HTTP2 in Apache Tomcat 2. Create a test jsp 3. Set response status as 408 4. Open jsp in chrome What is the expected behavior? Request should end properly What went wrong? Request loops infinitely until close the tab Did this work before? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 24.0 r0
,
Feb 22 2017
Could you please collect the net-log when you open the jsp and attach it to the issue? The instructions can be found here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Feb 22 2017
The author is unable to attach the logs. After clicking 'Save changes', the comment shows as Deleted. I have asked to file a new issue and attach the logs to it.
,
Feb 22 2017
A new issue 695225 has been opened with the logs attached. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted