Fix layout response for non-existent pages in RAV #2016
Merged
Conversation
This file contains 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
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.
Description / Motivation
The native fetch API was identifying the layout request as a complex request due to the explicitly set Content-Type header, which caused it to send an additional OPTIONS preflight request. This preflight request led to a CORS error, preventing the subsequent GET request from completing successfully. By removing the Content-Type header, the default headers for the HTTP request now satisfy the criteria for a simple request. This avoids triggering the preflight OPTIONS request and allows the GET request to complete as intended.
Testing Details
Types of changes