HTTP IN Node - handling preflight OPTIONS method

General
1

Hi,

I’m trying to debug / deal with a CORS issue and am struggling to deal with handling the preflight OPTIONS method.
My HTTP IN node looks like this:
[
{
"id": "options-preflight",
"type": "http in",
"z": "92427cf81310d58f",
"name": "OPTIONS /register",
"url": "/register",
"method": "options",
"upload": false,
"swaggerDoc": "",
"x": 180,
"y": 420,
"wires": [
[
"options-cors",
"add84e739de2ace9"
]
]
}
]

When the frontend tries to hit the “/register” endpoint I see no evidence that the OPTIONS method has been routed to this endpoint.

I am concerned that the UI doesn’t show “OPTIONS” in the dropdown - Does this imply that OPTIONS is not a valid verb in this node?

Sorry if I’ve not explained this very well. I’ll do my best to add any further info on request.

TIA

2

Hi,

In the end I gave up trying to resolve the CORS issue and changed my install to put Node Red behind an IIS reverse proxy and used URL ReWrite to route to a “new” /api endpoint.

Everything works perfectly and no CORS issues!