Separate Standard vs Non-standard Headers

[jordantrizz]

If possible common and standard HTTP headers should be placed in a single container while non-standard can be placed in another container. Additionally, provide an option to tag or categorize the non-standard headers to allow visitors to flag non-standard headers with notes so you get feedback on headers and can update the detection easily.

[hubertnguyen]

Hi Jordan, it's an interesting idea. Perhaps we could define what the standard headers are. What about:

0 accept-ranges connection content-length content-type date server vary

[jordantrizz]

100% that's a start!

[hubertnguyen]

I'll take a look. Another option is to add a toggle to show/hide the standard ones. And perhaps the setting could be saved in the browser.

[jordantrizz]

Please implement this :)

[hubertnguyen]

Rounding up the API then will take look

[hubertnguyen]

I just pushed an updated online test with the first version of this feature and There's a toggle button to show the hidden headers. By default, the following HTTP headers will be hidden (via CSS)

• 'accept-ranges', 'connection', 'content-length', 'content-type', 'server'

Also, HTTP Headers that contain the following text will also be considered standard, and hidden:

• 'link', 'date'

I left vary because traffic split can sometimes explain caching problems, but perhaps "standard vary" stuff could be detected and removed as well.

[jordantrizz]

Looks great!

[hubertnguyen]

Thanks @jordantrizz . I've added 7-8 more exclusions and that'll be in the next udpate later today. I'll close this one for now.