Repository navigation
config: document request restrictions of the no-cors fetch mode - #100
Merged
Merged
Conversation
In no-cors mode, the browser rejects methods other than GET, HEAD, and POST and drops request headers that are not CORS-safelisted, including HX-* headers, even for same-origin requests. The XML remarks and the HTMX 4.x configuration guide described only opaque responses, which apply only to cross-origin requests.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The documentation for
HtmxFetchMode.NoCorsdescribed only opaque responses. Inno-corsmode, the browser also:GET,HEAD, andPOST; for other methods,fetchthrows and HTMX raiseshtmx:error;HX-*headers,hx-headersvalues, or antiforgery token sent in a header, soIsHtmxRequest()and[HtmxRequest]do not recognize the request.Opaque responses apply only to cross-origin requests.