Skip to content

feat: handle Chrome CORS preflight private network header #308

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat: handle Chrome CORS preflight private network header #308

wants to merge 1 commit into from

Conversation

randing89
Copy link

Based on https://developer.chrome.com/blog/private-network-access-preflight/

Chrome will start sending a CORS preflight request ahead of any private network request for a subresource, which asks for explicit permission from the target server. This preflight request will carry a new header, Access-Control-Request-Private-Network: true, and the response to it must carry a corresponding header, Access-Control-Allow-Private-Network: true.

This fixes #290 and #236

@randing89 randing89 force-pushed the allow-private-network branch from 227b0a3 to cfe3c25 Compare November 6, 2023 10:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

No Configuration Options for Access-Control-Allow-Private-Network
1 participant
@randing89