|
|
|
|
|
|
by pornel
2780 days ago
|
|
|
Yes, fixing of AMP URLs is one of the motivators for this. Note that it's not "impersonation", as it requires the domain owner to sign the bundle, and Google can't alter the signed files. It's more like proxying of HTTPS traffic, but delayed. |
|
|
The signed html files likely include a script tag that downloads Google controlled JS. Such that AMP can continue to do whatever it wants.
Edit: "The AMP runtime is loaded via the mandatory <script src="https://cdn.ampproject.org/v0.js"></script> tag in the AMP document <head>."
https://www.ampproject.org/docs/fundamentals/spec#amp-runtim...
So you can use signed http and Google can't alter the files. But, if you make your page valid AMP for their cache, they certainly alter the page with their runtime. Adding the header at the top, intercepting things like left/right swipe for carousel and top-stories loaded pages, etc.