CORS route-specific override can conflict with connection defaults #2840
Labels
breaking changes
Change that can breaking existing code
bug
Bug or defect
security
Issue with security impact
Milestone
If the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route.
Also, try to automate Access-Control-Allow-Methods
The text was updated successfully, but these errors were encountered: