Menu
Below are two screenshots from the same version of Chrome. I would like to know when and why header names sometimes are displayed with different word capitalization and also when is the view source/view parsed toggle available? I've read the developer tools documentation which says nothing about it and tried to load pages in different ways. The only pattern i suspect is content compression, could that be it?
Update: nope seen both versions on sites using gzip
247
In Chrome, visit a URL(such as https://www.google.com ), right click, select Inspect to open the developer tools. Select Network tab. Reload the page, select any HTTP request on the left panel, and the HTTP headers will be displayed on the right panel.
Modify Headeropen Chrome developers toolbar Option + ⌘ + J (on macOS), or Shift + CTRL + J (on Windows/Linux). Press Command+Shift+P (Mac) or Control+Shift+P (Windows, Linux, Chrome OS) to open the Command Menu. In the User agent section disable the Select automatically checkbox.
View headers with browser development tools Within the page, right-click (for PC users) or command-click (Mac users) to view options, and then click Inspect. The Inspect feature will display the troubleshooting console, which will enable all of the available tools in a panel on the side of the window.
You can quickly search all of your source code by pressing Cmd + Opt + F ( Ctrl + Shift + F ).
It seems that it happens only for resources served over HTTP2/SPDY (compare this image served over HTTP2 with the same image served over HTTP). There is an old Chrome bug that proves that HTTP2/SPDY headers are being handled differently. I reported this as a bug here.
144
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
