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

Same authority primary and secondary server #6

Open
gaperik opened this issue Jun 16, 2016 · 1 comment
Open

Same authority primary and secondary server #6

gaperik opened this issue Jun 16, 2016 · 1 comment

Comments

@gaperik
Copy link
Contributor

gaperik commented Jun 16, 2016

A primary server may delegate to a secondary server run by the same provider as the primary server. This is a complementary usage to the cases where delegation is done to a separate CDN provider secondary server.

@gaperik
Copy link
Contributor Author

gaperik commented Oct 5, 2016

This case has been denoted "edge origin" in some discussions and I'm proposing to use that name henceforth to separate it from the CDN case and the BC proxy case.

This use case is an increasingly relevant one and as such one I would be ready do develop and discuss more at Seoul.

Now whether this has any actual impact on the OOB mechanism need to be discussed but one can easily see cases where the primary empowers an edge origin to do more than plain caching, for instance not use payload encryption.

What I still assume to be needed, if the browser http layer should implement oob support, is a mechanism by which the browser can verify that the secondary and the primary are indeed run by the same "authority" and consequently relax the requirement on encrypted payload.

@reschke reschke added the oob label Nov 18, 2016
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

2 participants