search

mdn / content

The content behind MDN Web Docs
https://developer.mozilla.org
Other
9.11k stars 22.46k forks source link

Missing HTTP header-specific pages (known) #1458

Open chrisdavidmills opened 3 years ago

chrisdavidmills commented 3 years ago

@hamishwillee commented on Mon Nov 09 2020

URL(s)

Request type

Details

There are many missing HTTP header pages - as linked from URLs above. In some cases there have paragraph docs, in others there is nothing. List from the main Headers Page:

jpmedley commented 3 years ago

@Elchi3 I think some of these are Google's creation, so I'm trying to get some help within Google. Can you point me to a header reference page that's up to date with regard to style and structure?

Elchi3 commented 3 years ago

I believe https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data is something that I wrote relatively recently.

jpmedley commented 3 years ago

I'm taking:

Will probably do more later.

I'm finding that some of these are values for headers, not headers themselves.

sideshowbarker commented 2 years ago

See also https://github.com/mdn/content/issues/1506#issuecomment-763172127

SphinxKnight commented 8 months ago

Cross-linking https://github.com/mdn/content/issues/15340 here for Refresh

Josh-Cena commented 1 month ago

The remaining links are:

Pinging @mdn/yari-content-http to decide what to do for each feature group: should we remove all mentions to it, remove the links only, or add pages? It's hard to tell which ones are supported and to what extent.

hamishwillee commented 1 month ago

what to do for each feature group: should we remove all mentions to it, remove the links only, or add pages? It's hard to tell which ones are supported and to what extent.

I don't know what you mean by this question - what page and headings are you referring to (I had a quick scan of the issue, but it has been a long time since it was posted and I have lost context).

Josh-Cena commented 1 month ago

I meant strictly in the context of my post: I have a list containing four groups of headers. I wonder if, for each group of headers, we should document them or not.

hamishwillee commented 1 month ago

For some reason, I'm not in that group. I've asked for access though. So here is "IMO":

I would drop Accept-Push-Policy Header Field as the spec is expired and archived. There is no evidence of implementation.

We should keep Signed HTTP Exchanges and document them. I don't know anything about them, but this spec is linked from https://developer.chrome.com/blog/signed-exchanges which indictates support from Chrome 73.

Remove Origin-Isolation - it isn't found in any search or present in the specs that to related to origin isolation.

For the non-standard cases we'll need more expertise - for example X-Robots-Tag does get quite a lot of mentions and I don't know of a "standard alternative", similarly X-Forwarded-For has a standard alternative, but I believe that X-Forwarded-For is a defacto standard. So we should keep it (if that is the case).