Option to allow private network access in CORS middleware. #2981
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.
Summary
The versions of Chrome browser after 130 require an additional header "Access-Control-Allow-Private-Network": "true" in PREFLIGHT interaction if you are trying to access f.i. a https://localhost resources, where uvicorn / starlette application is running. They promised to start blocking these requests altogether, but didn't, it's just a warning, but a very annoying one.
This is important for the current generation of AI applications if a local server with a Starlette application (not the MCP with FastApi) is used for interactions with a web-based AI application.
The allow_private_network parameter has been added to cors.py and the doc.
Checklist