Request for Unified Header for web servers to signal support
Reported by
homakov@gmail.com,
Mar 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 Steps to reproduce the problem: This is a feature request to fix an existing problem of so many headers and defaults we currently have. SOTA: 1 header would be a way for a website to signal that it supports version 1 of latest state-of-the-art how web apps should be built. It would include all those x-frame-options, x-nosniff etc Basically, one header to set all the attributes, headers and things we do manually just to stay compatible. I've made a post with more details here https://medium.com/@homakov/request-for-a-new-header-state-of-the-art-9a1935bbad72#.d8qnjp1zd Interested to hear your opinion! What is the expected behavior? What went wrong? - Did this work before? N/A Chrome version: 56.0.2924.87 Channel: n/a OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 25.0 r0
,
Mar 23 2017
hamakov@, thanks for posting your opinion! As far as I understand, you seem to be proposing a new header for HTTP protocol, which is larger than only Chrome, and unfortunately this is a place for discussing Chrome or Chromium specific bugs. I'd think better place for discussing such things is IETF (where HTTP standard is discussed) or W3C (where any web APIs are discussed). At this point, we cannot do anything for Chrome. |
||
►
Sign in to add a comment |
||
Comment 1 by erikc...@chromium.org
, Mar 22 2017