Support Private Network Access (RFC1918) #793
Comments
|
https://developer.chrome.com/blog/private-network-access-update/ talks about Chrome's timeline for this |
8 tasks
|
This issue has been inactive for 180 days |
|
Chrome 105 seems to now be actively blocking PNA (localhost in a development workflow). Until this issue is picked up, and purely as a temporary stop-gap, I added the following to allow continuing my debug workflow https://github.com/http-party/http-server/blob/master/lib/http-server.js#L102 This is purely a temporary solution for anyone with a similar debug/local dev workflow need and nothing more. As the OP specified, this should be controlled via the inclusion of the Access-Control-Request-Private-Network header in the request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the problem this feature will solve?
See this doc. Eventually public websites that hit local addresses will require the server to respond to a pre-flight request for the Access-Control-Request-Private-Network header. http-server should support an option for this like it does for --cors.
Describe the solution you'd like
--private-network-access (or something better named) should respond to these pre-flight requests appropriately with Access-Control-Request-Private-Network: true.
Alternative Solutions
I'm not sure there are any, if this RFC is put into play by all browsers.
Additional context
The text was updated successfully, but these errors were encountered: