3 ms·
They're actually going to fix the URL problem once and for all using [Cross-Origin Server Push][1] in the upcoming Signed HTTP Exchanges standard. Here's their
by Ajedi32 9y ago
They're actually going to fix the URL problem once and for all using [Cross-Origin Server Push][1] in the upcoming Signed HTTP Exchanges standard. Here's their blogpost on that: https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/ https://amphtml.wordpress.com/2018/01/09/improving-urls-for-...
[1]: https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses-02#section-4 https://tools.ietf.org/html/draft-yasskin-http-origin-signed...
- ThbTs4wbXC9Qjv 9y agoThe standard authored by J. Yasskin from Google? Self-serving their own interests much?
- ec109685 9y agoAnd every other site that links off.
- dfabulich 9y ago(Author here.) The "Signed HTTP Exchanges standard" is part of the Web Packaging standard, which is, indeed, the whole point of the article. https://github.com/WICG/webpackage https://github.com/WICG/webpackage