-
-
Notifications
You must be signed in to change notification settings - Fork 659
Doc cors spec compliance #4202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc cors spec compliance #4202
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
##### Garbage Collection | ||
#### CORS | ||
|
||
Unlike browsers, Undici does not implement CORS (Cross-Origin Resource Sharing) checks by default. This means: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a reference to the relevant part of the fetch spec would be useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would a link to this section suffice? If so I can address in a separate PR.
https://fetch.spec.whatwg.org/#cors-check
##### Garbage Collection | ||
#### CORS | ||
|
||
Unlike browsers, Undici does not implement CORS (Cross-Origin Resource Sharing) checks by default. This means: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unlike browsers, Undici does not implement CORS (Cross-Origin Resource Sharing) checks by default. This means: | |
Unlike browsers, Undici does not implement CORS (Cross-Origin Resource Sharing) checks. This means: |
"by default" makes it sound like there is a way to enable CORS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Will address if a new PR is created for the suggestion above.
This PR adds a section to the documentation detailing the default CORS behaviour mentioned in #4179.