mdn
Remove Transfer Encoding "identity" value
MDN URL
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding
What specific section or headline is this issue about?
Syntax and Directives
What information was incorrect, unhelpful, or incomplete?
Here Identity Transfer-Encoding is missing: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding
Here it's not: https://developer.mozilla.org/es/docs/Web/HTTP/Headers/Transfer-Encoding https://developer.mozilla.org/ja/docs/Web/HTTP/Headers/Transfer-Encoding https://developer.mozilla.org/ko/docs/Web/HTTP/Headers/Transfer-Encoding https://developer.mozilla.org/ja/docs/Web/HTTP/Headers/Transfer-Encoding https://developer.mozilla.org/pt-BR/docs/Web/HTTP/Headers/Transfer-Encoding https://developer.mozilla.org/zh-CN/docs/Web/HTTP/Headers/Transfer-Encoding
What did you expect to see?
I expect to see Identity documented in all languages or undocumented in all languages...
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
I can create a pull request for it, But I'm not sure if I should add or remove it...
If it's in every localized version but missing in en-US, the only correct interpretation is that the localized versions are not updated. Here it was removed in https://github.com/mdn/content/pull/8016, so it should be removed from all localized versions.
Thank you, That was crazy fast!
Not sure I would remove it, I think I would have set it as deprecated...
That would depend on whether browsers support it or not, which tends to be a hard question to answer for HTTP things.
@queengooborg You may know something about this, but do you know if Transfer-Encoding: identity is supported in browsers or how we may test this?
I actually don't know much about the support history of HTTP headers, much less that specific header and value. However, I think it's safe to proceed with removing mention of it in localized content as well -- the PR that removed mention of it from English content was three years ago, and the RFC document that removed the value is ten years old!
The question is what makes more sense in this situation working with the latest RFC, working with the Browser capabilities or with Server capabilities. I think in this case Server capabilities matters more because this specific header is rarely used by Browsers... Actually I think it's used by hackers (with HTTP Smuggling) more the Browsers and Legitimate clients. I saw some browser compatibility but I can check about the top 3-4 like nginx and apache.