Skip to content
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

Discrepancy between how CORS-preflight fetch (append) and PNA (set) add headers #132

Open
jub0bs opened this issue Mar 25, 2024 · 0 comments

Comments

@jub0bs
Copy link
Contributor

jub0bs commented Mar 25, 2024

In CORS-preflight fetch, preflight-request headers Access-Control-Request-Method and Access-Control-Request-Headers are appended to the preflight request's header list, e.g.

Append (Access-Control-Request-Method, request’s method) to preflight’s header list.

However, in section 3.4.2 of the draft report (more specifically, in step 10.2.1.1), request header Access-Control-Request-Private-Network is not appended to, but set in the preflight request's header list:

Set "Access-Control-Request-Private-Network" to "true" in preflight’s header.

I'm not sure whether this discrepancy is warranted. I believe it to be inconsequential (?) but, for consistency, adopting the Fetch standard's wording/operation (append rather than set) would perhaps be preferable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant