How to handle OPTIONS requests?

[geiszla]

In the past we have handled HTTP OPTIONS requests inside the corresponding route's loader function, however recently this has stopped working. Right now I can't see the OPTIONS request triggering anything except the morgan logging plugin.

E.g., I can see the OPTIONS request for the following route logged by morgan, but neither handleRequest inside entry.server.jsx, nor the loader function exported from customerAccount.earn trigger.

My end goal is adding the proper cors headers to the preflight request, but it seems like Remix sends the 204 response back without running any handlers for the request.

How could I debug this issue further? In particular, what handlers the OPTIONS request should trigger that I could inspect on what's happening?

[Blaumaus]

Did you manage to solve this?

[geiszla]

I've found a Vite option, server: { cors: { preflightContinue: true } }, which fixes this issue. I'm not sure if this is the intended way to handle OPTIONS requests, and I also don't know why this just came up now (we've been handling OPTIONS requests in this project before without issues and without this Vite option set).

[mehmettekn]

Hi @geiszla, thank you for sharing this. I wasted about a whole morning and part of an afternoon until I stumbled upon this post. Oh, the beauty of web development! :)