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

Q: referrer from signed http exchanged page #206

Closed
Jxck opened this issue Jun 9, 2018 · 4 comments
Closed

Q: referrer from signed http exchanged page #206

Jxck opened this issue Jun 9, 2018 · 4 comments

Comments

@Jxck
Copy link

Jxck commented Jun 9, 2018

1, navigate to https://example.com/a.sxg
2, a.sxg is signed by https://example.net so browser display it as https://example.net
3, clicking the link on https://example.net

in request of 3, which origin should on referrer header example.com (actual) or example.net (display) ?
(spec seems not mention this: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html)

@kinu
Copy link
Collaborator

kinu commented Jun 12, 2018

That should be example.net I believe. Also example.net is the actual origin once UA is navigated to the exchange. The loading sketch in the explainer discusses some of these (while not clearly specifying details like referrers)

@Jxck
Copy link
Author

Jxck commented Jun 12, 2018

is there any plan to add actual url(example.com) on request header like referrer ?

@jyasskin
Copy link
Member

There's no plan to add a new Referer-like header that identifies the physical URL of the referrer. It's always possible, of course, given a strong enough use case.

@jyasskin
Copy link
Member

#433 discusses the architectural question here.

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

No branches or pull requests

3 participants