Hey there! We've found the following might help you get unblocked faster:

• 🧵 Cors issue with Railway's edge file server intercepting OPTIONS requests before they reach FastAPI.

• 🧵 CORS Issues

• 🧵 Slow private networking responses with nginx

• 🧵 CORS Errors on Express API Deployed to Railway

If you find the answer from one of these, please let us know by solving the thread!

@brody can we keep this private till it is actually resolved. I don't know if I would have to share private information or not yet and would like to get a resolution fast if it means I have to share some information to help y'all debug faster

Also, another thing I noticed is that I can see the request when I filter the "HTTP logs" which seems to return a 204 status but within my deploy logs I can't find anything related to it.

We do not filter headers or the OPTIONS method under any circumstances, so since this isn't an issue with our platform or product, I have opted to open this up to the community for them to help you, as we cannot provide application-level support, but the community can help.

Hmm, I'll try to debug it but it seems like only the OPTIONS request is somehow are being filtered. I have a logger to log any incoming requests (even failed ones) and I don't see anything incoming but the proxy returns a 204 status code.

There is nothing on our end that would return a 204; that is what your app is returning.

okay, yeah lemme debug it more before I waste your time

I'll drop out here since this isn't an issue with our platform or product. Any further support will be community-provided for this thread.

But I wish you all the best as you debug this!

Def a me issue. Sorry for bothering the team.