RestServer: handle CORS preflight OPTIONS #396
Merged
+31
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Parse OPTIONS requests and reply with 204 + CORS headers Signed-off-by: drslebedev <dr.s.lebedev@gmail.com>
drslebedev
temporarily deployed
to
configure coverage
GitHub Actions
Inactive
drslebedev
temporarily deployed
to
configure coverage
GitHub Actions
Inactive
drslebedev
had a problem deploying
to
configure coverage
GitHub Actions
Failure
drslebedev
temporarily deployed
to
configure coverage
GitHub Actions
Inactive
drslebedev
temporarily deployed
to
configure coverage
GitHub Actions
Inactive
drslebedev
temporarily deployed
to
configure coverage
GitHub Actions
Inactive
RalphSteinhagen
approved these changes
Jan 21, 2026
drslebedev
temporarily deployed
to
configure coverage
GitHub Actions
Inactive
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes CORS preflight handling for the REST server.
Previously, browser preflight
OPTIONSrequests could be mis-parsed and end up on the normal request path, which caused CORS failures even though regular responses already includedAccess-Control-Allow-Origin: *. NowOPTIONSis detected and answered with204+ CORS headers.