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

Fetch: From-Origin #80

Closed
annevk opened this issue Apr 10, 2018 · 2 comments
Closed

Fetch: From-Origin #80

annevk opened this issue Apr 10, 2018 · 2 comments

Comments

@annevk
Copy link
Contributor

annevk commented Apr 10, 2018

If there are any concerns around From-Origin as outlined at whatwg/fetch#687 that'd be good to know.

There's also an alternative proposed in that thread: an Origin header that's included for every request. My concern with that header is that it makes referrer leaking worse, unless we restrict it to revealing one of same-origin, same-site, or cross-site.

(An architectural question here is that this is yet another piece of web infrastructure proposing a dependency on Public Suffix. Given that WebAuthn does it too, I kinda think we've already taken the decision to embrace it, but it's worth calling out.)

@annevk
Copy link
Contributor Author

annevk commented May 7, 2018

We've discussed this internally and those partaking in that discussion agreed on worth prototyping as a position, provided the feature only affects whether the fetch in question succeeds or fails and has no side effects beyond that.

@annevk
Copy link
Contributor Author

annevk commented Jun 18, 2018

Closing this in favor of https://bugzilla.mozilla.org/show_bug.cgi?id=1459573. It probably doesn't need a new entry on the dashboard.

@annevk annevk closed this as completed Jun 18, 2018
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