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
My application now seems to be responding with 200 OK to OPTIONS requests for arbitrary paths, such as /bar:
Granted it's not responding with any valid CORS response headers, but I'm wondering if this is intended or if I'm doing something wrong. In trying to pare this down, it seems even an empty config displays this behavior:
config.middleware.insert_before0,Rack::Corsdoend
Is there any way to strictly only respond to requests for /foo? Just getting started and trying to wrap my head around the gem.
The text was updated successfully, but these errors were encountered:
I'm trying to add CORS to a Rails app just for a specific path,
/foo
. With the following rack-cors config:My application now seems to be responding with 200 OK to OPTIONS requests for arbitrary paths, such as
/bar
:Granted it's not responding with any valid CORS response headers, but I'm wondering if this is intended or if I'm doing something wrong. In trying to pare this down, it seems even an empty config displays this behavior:
Is there any way to strictly only respond to requests for
/foo
? Just getting started and trying to wrap my head around the gem.The text was updated successfully, but these errors were encountered: