Please do not lower-case header names
Reported by
jidanni@gmail.com,
Oct 25 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: Please do not lower-case header names. It may "look good" but it is not what the server sent. What is the expected behavior? Cache-Control: max-age=60, private, private Content-Encoding: gzip Content-Type: application/json; charset=utf-8 What went wrong? cache-control:max-age=60, private, private content-encoding:gzip content-type:application/json; charset=utf-8 Did this work before? N/A Chrome version: 61.0.3163.100 Channel: n/a OS Version: Flash Version: In fact, you don't also offer the raw headers anymore. Just the cooked headers. How would you feel if somebody instead changed lower case to upper case?
,
Oct 25 2017
Thank you for the issue! Can we have a bisect, if this has regressed in M50?
,
Oct 26 2017
Issue has not regressed in M50. Same behaviour is seen from older chrome version. We are treating all the issues seen from M-50 as Non-regression during bug triaging. Hence changing the label to Non-Regression and marking as Untriaged. Please change if not the case. Thanks!
,
Dec 13 2017
,
Dec 19 2017
This appears to be fixed. I see proper case in both stable (63.0.3239.108) and my local ToT build. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sc00335...@techmahindra.com
, Oct 25 2017Components: -Platform>DevTools Platform>DevTools>Network
Labels: M-64 Needs-Triage-M61 Triaged-ET OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)