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

null client is not correct for fetching origin policies #75

Closed
domenic opened this issue Feb 18, 2020 · 0 comments · Fixed by #76
Closed

null client is not correct for fetching origin policies #75

domenic opened this issue Feb 18, 2020 · 0 comments · Fixed by #76
Assignees

Comments

@domenic
Copy link
Collaborator

domenic commented Feb 18, 2020

We need to instead reuse the client from the original fetch. This ensures proper HTTP cache partitioning per whatwg/fetch#943, and probably several other good things.

This issue covers the network fetch in https://wicg.github.io/origin-policy/#update-an-origins-origin-policy. #73 covers the cache fetch in https://wicg.github.io/origin-policy/#retrieve-the-cached-origin-policy which has other problems detailed there.

@domenic domenic self-assigned this Feb 18, 2020
domenic added a commit that referenced this issue Feb 18, 2020
Closes #75. Note that we now have to explicitly set the referrer policy to null to preserve the resolution of #65.
domenic added a commit that referenced this issue Feb 18, 2020
Closes #75. Note that we now have to explicitly set the referrer policy to "no-referrer" to preserve the resolution of #65.
domenic added a commit that referenced this issue Feb 19, 2020
Closes #75. Note that we now have to explicitly set the referrer policy to "no-referrer" to preserve the resolution of #65.
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

Successfully merging a pull request may close this issue.

1 participant