HTTP > Content Length : Added to safelisted response header in specific versions

[hamishwillee]

The Content-Length HTTP response header got added to the CORS safelisted response headers in a late revision to the spec.

• This was just added to FF list in FF87 - https://bugzilla.mozilla.org/show_bug.cgi?id=1460299
• was added to "non Blink Edge" but the info on version is now hidden behind a broken link to the original bug https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/17440391/
• Added to Safari/Webkit https://bugs.webkit.org/show_bug.cgi?id=185473
• Chrome - can't find any mention.

So the question is, "what is the best way to add this to BCD". My thought was as a subfeature "cors_response_safelist" with FF87 and Safari added (either with version if I can find it or true, the rest null). Is that reasonable?

Who can we ask about Chrome/Blink?

@ddbeck Advice appreciated please.

[ddbeck]

• Chrome - can't find any mention.

For Chrome, I found this: https://storage.googleapis.com/chromium-find-releases-static/5e9.html#5e97971dd8d45819d5758b2a5fd53ebdce7e7138

So the question is, "what is the best way to add this to BCD". My thought was as a subfeature "cors_response_safelist" with FF87 and Safari added (either with version if I can find it or true, the rest null). Is that reasonable?

Do you mean a subfeature of http.headers.Access-Control-Expose-Headers or some other feature?

[ddbeck]

• as added to "non Blink Edge" but the info on version is now hidden behind a broken link to the original bug https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/17440391/

Oh and this one I wasn't able to sort out. A shame Microsoft took that site offline. Ideally, a test case that we could run on old versions in BrowserStack or SauceLabs would settle it. If that's too much hassle, ≤79 would be satisfactory.

[hamishwillee]

Do you mean a subfeature of http.headers.Access-Control-Expose-Headers or some other feature?

My thinking was to add it as a subfeature of Content-Length. But probably it should be added to all of the safelisted headers: Cache-Control, Content-Language, Content-Length, Content-Type, Expires, Last-Modified, Pragma.

Currently the information is in a table at the top of pages, but would not hurt for it to be in BCD, especially now this is a compatibility thing.

[ddbeck]

OK. That makes sense. I'd welcome a PR that does this for one or two of the headers, so we can see what it looks like before filling them out for every single one.

[hamishwillee]

Excellent. Test case in #9456