Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change to "Forbidden header name" #22502

Open
annevk opened this issue Nov 23, 2022 · 4 comments
Open

Change to "Forbidden header name" #22502

annevk opened this issue Nov 23, 2022 · 4 comments
Labels
Content:Glossary Glossary entries Content:HTTP HTTP docs help wanted If you know something about this topic, we would love your help!

Comments

@annevk
Copy link
Contributor

annevk commented Nov 23, 2022

MDN URL

https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name

What specific section or headline is this issue about?

Forbidden header name

What information was incorrect, unhelpful, or incomplete?

In whatwg/fetch#1541 we are making a change to the standard upon which this information is based. It'll now include some more headers (though only when they have particular values).

What did you expect to see?

I did not expect anything, but given the change mentioned above I hope to see it reflected in the future.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

@github-actions github-actions bot added Content:Glossary Glossary entries needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. and removed Content:Glossary Glossary entries labels Nov 23, 2022
@Josh-Cena Josh-Cena added Content:HTTP HTTP docs Content:Glossary Glossary entries help wanted If you know something about this topic, we would love your help! waiting for implementations Waiting for feature to be implemented in browsers and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Nov 23, 2022
@sideshowbarker
Copy link
Collaborator

https://wpt.fyi/results/fetch/api/basic/request-forbidden-headers.any.html shows all engines already passing the current relevant tests. @annevk, does that mean all engines already implement what’s in this spec change? Or instead does it mean the tests aren’t up to date?

@annevk
Copy link
Contributor Author

annevk commented Nov 28, 2022

They already implement this change.

@sideshowbarker
Copy link
Collaborator

@Josh-Cena is there some other reason you labeled this with “waiting for implementations”? Or shall we remove it that?

@Josh-Cena
Copy link
Member

Oh, I was looking at the spec PR and I saw there were no implementation bugs filed. I didn't see that it's already implemented.

@Josh-Cena Josh-Cena removed the waiting for implementations Waiting for feature to be implemented in browsers label Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:Glossary Glossary entries Content:HTTP HTTP docs help wanted If you know something about this topic, we would love your help!
Projects
None yet
Development

No branches or pull requests

3 participants