jetty / jetty/jetty.project

The Access-Control-Allow-Private-Network CORS header recently introduced in Google Chrome

Open
#7,642 5 comments 0 reactions 0 assignees View on GitHub
Bug Specification
Dominant language
Java
Stars
4.1k
Forks
2k
Avg merge
3d 56m
Merged PRs (30d)
48

Description

**9.2.26+**

**OpenJDK 17**

**Windows 10**

Getting an error message when a remote page tries to access a local Jetty Web server on 127.0.0.1:8080 -

"Access to XMLHttpRequest at 'http://127.0.0.1:8080/api' from origin 'https://scratch.ed.bot' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Private-Network' header was present in the preflight response for this private network request targeting the `local` address space.

It seems a new header has been introduced. How can I configure this response header with the CrossOriginFilter?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.