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
However, contrary to popular belief and according to the Fetch standard, allowing those request headers is never necessary. As so-called forbidden request headers, they're indeed handled by the browser, not by the client.
You can safely drop those three elements from that list.
The text was updated successfully, but these errors were encountered:
jub0bs
changed the title
Listing Origin as an allowed request header is never necessary
Listing Origin, DNT, or Accept-Encoding as allowed request headers is never necessary
Apr 2, 2023
Understanding CORS
Python Version
No response
Django Version
No response
Package Version
No response
Description
The README explicitly lists
"accept-encoding"
,"dnt"
, and"origin"
in theCORS_ALLOW_HEADERS
list:However, contrary to popular belief and according to the Fetch standard, allowing those request headers is never necessary. As so-called forbidden request headers, they're indeed handled by the browser, not by the client.
You can safely drop those three elements from that list.
The text was updated successfully, but these errors were encountered: