-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
📝 [Proposal]: Add Support for the Private Network Access CORS Header Access-Control-Request-Private-Network
#2804
Comments
This is really interesting. But I was just curious how are we avoiding pre-flight requests in this case. To access a private resource wouldn't the browser still need to make an What I'm confused about is that isn't it up to the browser to decide automatically when a pre-flight request needs to be sent. Either way, it would be sending a pre-flight request any way? So how are we avoiding additional pre-flights? |
@Behzad-Khokher |
sure we can do this |
@ReneWerner87 I can look into this. May I self assign? |
Thx |
This is still in draft and has not been accepted as a standard. https://wicg.github.io/private-network-access/ recommend against adding at this time. |
Fixed via #2908 will be a new festure in Fiber v3 |
Feature Proposal Description
Add CORS Middleware Support for the Private Network Access CORS Header
Access-Control-Request-Private-Network
to avoid additional preflight/timeout time cost.Alignment with Express API
Express.js's CORS middleware has not been updated yet.
HTTP RFC Standards Compliance
API Stability
It seems that Chrome 104 has already shipped this header.
Feature Examples
Example Request
Expected Response for the Example Request
Checklist:
The text was updated successfully, but these errors were encountered: