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 am not sure if sending such a header for GET requests violates a spec, but since the header specifies the content type of the body, and GET requests doesn't have a body, the header is at best unhelpful. Also, browsers (Chrome, Firefox…) don't send that header for GET requests.
As noted by Brian, a value of none seems invalid, as MIME types must have the form type/subtype, so this is definitely something we should take care of.
I am not sure if sending such a header for GET requests violates a spec, but since the header specifies the content type of the body, and GET requests doesn't have a body, the header is at best unhelpful. Also, browsers (Chrome, Firefox…) don't send that header for GET requests.
+1 from user
The text was updated successfully, but these errors were encountered: