Open ops1ops opened 3 years ago
The RFC 7230 ((HTTP/1.1): Message Syntax and Routing ) section 3.2 specifies:
Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.
Thus, lower-cased header names are valid and should be accepted by any compliant server.
Can i change the case of headers being sent to server in preflight request? I talk about Access-Control-Request-Headers, so superagent sending Access-Control-Request-Headers: content-type, but my server expects Content-Type and CORS fails