You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: