You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe it could be an edge case, considering that an empty header value is not valid per RFC-7230. Don't know why Github sends x-accepted-oauth-scopes without any value though.
Not 100% TBH. I did a quick research and some users were saying that empty header values were not valid unless some specific cases, since they could introduce security risks. It would be nice to know exactly if they are valid or not. Source. However, I found a StackOverflow answer saying that empty headers are valid if they don't contain any characters, so I'm quite confused if they're valid or not.
The source you linked to includes a reference to mnot who should be taken as authoritative and it aligns with what I'm saying. He's a spec person. I'm a browser person. We agree.
I too am sorry that people have trouble reading specifications but this really isn't complicated. The ABNF isn't ambiguous and even the prose isn't terrible it says a field-value, and a field value is defined as a * of thing and that means the thing is optional.
Describe the bug
HTTP Response headers with empty values have their header name listed with a trailing
:
To Reproduce
sh
friendly shell with a cooperativenc
:See:
Expected behavior
Screenshots
Desktop (please complete the following information):
Additional context
GitHub sends
x-accepted-oauth-scopes:
at timesThe text was updated successfully, but these errors were encountered: