iOS 11: Apple beats Google at AMP pages cheat

Various AMP pages.

(Picture: Heise)

The latest version of Mobile Safari detects if Google intermediate acceleration servers are used and then restores the original URL restored.

Google's Accelerated Mobile Pages (AMP) with which mobile websites can be accelerated, are not without controversy - also because the AMP versions of pages are cached on Google's own servers and thus have a rewritten URL. If you want to pass on links to such offers, the receiver ends up itself again on a AMP page should he use Android or iOS devices. Apple will do in the upcoming version of Mobile Safari the problem now, which is part of appearing in the fall iOS. 11 The have found developers who have tested the latest beta version.

AMP URL is normalized

Used to test the parts feature of Apple's browser, that if there is an AMP site. If so, is not the AMP statement (about "https://www.google.com/amp/www.example.com/amp.doc.html") Via iMessage & forwarded Co., but the URL to the original page (about "https://www.example.com/doc.html"). This also works if you add the URL of the iOS 11 Safari Reading List, which can be also match the Mac way.

From the user's perspective, the new Safari in iOS behavior can be interpreted as good or bad 11 - who likes fast loading of AMP pages, this gets will no longer be delivered for forwarded links. but many users are also likely to estimate that Apple now prefers the original URLs that actually point to the servers of the respective sides. So the journalist Federico Viticci writes on Twitter, it was "very beautiful"That Apple when sharing AMP pages "AMP waste from the URL" automatically removed.

Very nice: when sharing AMP pages to iMessage or Reading List, iOS 11 Safari automatically Removes AMP's crap from the URL. Go Apple ὄd pic.twitter.com/aHgSMcofUv

- Federico Viticci (@viticci) August 23, 2017

AMP as a golden cage?

AMP applies in particular since the introduction of traditional web developers as a thorn in the side. Although the technology speeds up the loading pages significantly - for example, when AMP pages calls from the Google search. But the service is also Google again significantly more power. So wrote c't editor Herbert Braun in a widely read commentary, he thought AMP for a "gilded cage",

For example scripts from Google's servers must be included that allow a user tracking. "but Google wants to know not only about each zappers: It wants the content itself, the Google Search from your mobile device does not lead to the content provider, but the AMP cache under www.google.com/amp/.." There was no opt-out. "These links make the AMP exit difficult." That seems to be seen at Apple too.

[Update 08/24/17 16:05:] The Technical Lead of Google's AMP project, Malte Ubl writes in a comment on Hacker News that they had a passing of the original links (Canonical URL) from Apple and other browser manufacturers at AMP pages "specifically requested", The AMP policy meant that a Canonical URL of an article while sharing "whenever technically possible" should be issued. The browser changes in Safari makes this possible. "We can not wait that the other manufacturers do."

However, Safari have a "special case" implemented and we hope to have a "more generic solution"In which a browser shares the original URL by default. Why Google's in-house Chrome browser on iOS AMP pages continue only AMP links passes, remains open.(BSC)