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
{{ message }}
This repository has been archived by the owner on Jan 16, 2021. It is now read-only.
Intuitively, I would expect these results to be the same.
RFC 7231 doesn't appear to weigh in explicitly on this issue, but does seem to imply that the two should be treated as equivalent (emphasis added):
The asterisk "" character is used to group media types into ranges, with "/*" indicating all media types ...
A request without any Accept header field implies that the user agent will accept any media type in response.
Although maybe there are valid reasons not to consider them the same.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm not 100% sure this is a bug, but intuitively, it doesn't make sense to me.
Consider this code:
And it's respective output:
Intuitively, I would expect these results to be the same.
RFC 7231 doesn't appear to weigh in explicitly on this issue, but does seem to imply that the two should be treated as equivalent (emphasis added):
Although maybe there are valid reasons not to consider them the same.
The text was updated successfully, but these errors were encountered: