Document the the X-Requested-With HTTP header

[techsin]

MDN URL: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers

What information was incorrect, unhelpful, or incomplete?

X-Requested-With link is broken!

Specific section or headline?

It's under Other

What did you expect to see?

documentation about X-Requested-With header

Did you test this? If so, how?

click the link

MDN Content page report details

• Folder: en-us/web/http/headers
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/http/headers/index.html
• Last commit: fc36604
• Document last modified: 2021-03-19T23:16:59.000Z

[sideshowbarker]

Yeah the cause is, nobody has yet written the https://developer.mozilla.org/docs/Web/HTTP/Headers/X-Requested-With article.

So the task for whoever works on this would be to write that article.

[techsin]

how do I find out who works on that?

[hamishwillee]

@techsin This is open source, so it could be anyone - you're most welcome to take it on. At some point if my list of things got small enough I might take it on.

[himanshugarg]

Using a link checker found the following headers with broken links. Do we need all of these to have their own:-

• Viewport-Width
• Width
• Max-Forwards
• Origin-Isolation
• X-Download-Options
• X-Permitted-Cross-Domain-Policies
• X-Powered-By
• Last-Event-ID
• Ping-From
• Ping-To
• Report-To
• Sec-WebSocket-Key
• Sec-WebSocket-Extensions
• Sec-WebSocket-Protocol
• Sec-WebSocket-Version
• Accept-Push-Policy
• Accept-Signature
• Push-Policy
• Signature
• Signed-Headers
• Service-Worker-Allowed
• X-Firefox-Spdy
• X-Pingback
• X-Requested-With
• X-Robots-Tag
• X-UA-Compatible

[techsin]

say if someone wanted to fill out the docs, would they be using w3specs as a reference?

…

On Mon, May 24, 2021 at 2:18 AM Himanshu ***@***.***> wrote: Using a link checker found the following headers with broken links:- - Viewport-Width - Width - Max-Forwards - Origin-Isolation - X-Download-Options - X-Permitted-Cross-Domain-Policies - X-Powered-By - Last-Event-ID - Ping-From - Ping-To - Report-To - Sec-WebSocket-Key - Sec-WebSocket-Extensions - Sec-WebSocket-Protocol - Sec-WebSocket-Version - Accept-Push-Policy - Accept-Signature - Push-Policy - Signature - Signed-Headers - Service-Worker-Allowed - X-Firefox-Spdy - X-Pingback - X-Requested-With - X-Robots-Tag - X-UA-Compatible — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4178 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDS254ROUJ4JAYDGAAUIPTTPHVT5ANCNFSM43BXTVRQ> .

[hamishwillee]

Yes. Though there are plenty of headers that are not in W3C specs - e.g. the Sec-* ones I talk about here: #4907 (comment)

Further there may be some not even mentioned on MDN yet.

But yes, over time we should aim to document all headers that have been broadly implemented. I will get to Viewport-Width and Width sometime soon as part of #4907

FYI very soon most of these broken links will start showing up as red links. No link checker required.

[Josh-Cena]

Duplicate of #1458