Hacker News Reader

Here's the real question - how is this implemented in chrome? are signed exchange website that are clicked in google search page and whose url is switched is still running the google search page's code?

If this is so, and it only works for google search's page and not some generic web strategy, this is a massive breach of browser/web-content separation, bigger then even the auto-sign-in to google from chrome.

View on HN

Good question.

Conceptually, you can think of a signed exchange as a 301 redirect to a new URL which has already been cached by the browser (so there is no 2nd network event). The cache was populated by the contents of the signed exchange, assuming the signature validates.

There is no "reaching into the document" from the previous click or anything weird like that.

I just wanted to say a quick thank you for going out of your way to answer to many questions here. Despite the obviously hostile environment (I have some reservations about AMP myself), your answers have been very clear, informative and level-headed, so thanks for that.

I appreciate the comment. My goal here is simply to correct some of the misunderstandings about the format, rather than express opinions.

Reply on news.ycombinator.com