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
Although method names are case-sensitive, Gorilla's CORS middleware takes the non-standard approach of normalising method names by uppercasing them. Such unwarranted case normalisation causes problems for clients that send requests whose method is not uppercase—and not some case-insensitive match for one of DELETE, GET, HEAD, OPTIONS, POST, or PUT, names for which the Fetch standard carves out an exception.
Expected Behavior
Gorilla should not normalise the case of allowed method names.
Steps To Reproduce
Here is a (failing) test case that illustrates the problem:
Is there an existing issue for this?
Current Behavior
Although method names are case-sensitive, Gorilla's CORS middleware takes the non-standard approach of normalising method names by uppercasing them. Such unwarranted case normalisation causes problems for clients that send requests whose method is not uppercase—and not some case-insensitive match for one of
DELETE
,GET
,HEAD
,OPTIONS
,POST
, orPUT
, names for which the Fetch standard carves out an exception.Expected Behavior
Gorilla should not normalise the case of allowed method names.
Steps To Reproduce
Here is a (failing) test case that illustrates the problem:
Current result:
Anything else?
More about this topic in one of my recent blog posts.
The text was updated successfully, but these errors were encountered: