Fixes CORS for meshtasticd to allow use of clients on other origins #5463
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am receiving
404 Not Found
when clients using@meshtastic/js
in a web browser make anOPTIONS
request to/api/v1/toradio
and/api/v1/fromradio
on ameshtasticd
node when using a custom client on another origin.This results in not being able to communicate with the node.
#5386 fixed this when connecting to the built in ESP32 server over WiFi, this PR fixes the same thing but for the
meshtasticd
server as well :)It seems there was already checks for the options requests, but they wouldn't ever be hit since only
GET
andPOST
handlers were registered.I also changed the
http_verb
comparison to usestrcmp
as the==
check never passed.