Closed bogeychan closed 1 month ago
According to RFC 2616, header field is case-INsensitive which means either case should work just fine.
Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive
So, in my opinion, it's unlikely that we would make a (soft) breaking change for that
What version of Elysia is running?
1.1.16
What platform is your computer?
WSL Ubuntu
What steps can reproduce the bug?
new Elysia().get("/", () => "lower case content-type").listen(3000);
What is the expected behavior?
to have all these headers upper case by default: CORS-safelisted
maybe switch behaviour and make all upper case
What do you see instead?
Additional information
For more details: https://github.com/elysiajs/elysia-cors/issues/48#issuecomment-2371926760
Have you try removing the
node_modules
andbun.lockb
and try again yet?yes