In Mobile Safari AMP pages that include <iframe>s appear to be making network requests to the follow path "/amp_preconnect_polyfill_404_or_other_error_expected._Do_not_worry_about_it". This can be observed by monitoring network traffic on the device. It will also show with great frequency in the network logs of servers delivering the <iframe>d experience.
This preconnect polyfill is not documented (except for a few Stack Overflow questions) and may come as a surprise to those hosting an <iframe>d experience on an AMP page. The "_Do_not_worry_about_it" portion of the path does not allay any suspicions and does not provide any additional information about the feature.
This feature should be documented in AMP with enough detail for developers to understand and anticipate this behavior. I would also suggest that the preconnect URL reference the documentation so the documentation is more discoverable when someone does observer the URL pattern.
Observed in Mobile Safari.
1506041909031
/to @bpaduch I know validator has a "errors" doc for errors and their meanings, we may wanna start one for AMP JS too.
Hi, has this issue been resolved? I would like to help :)
@Bubblemelon - It hasn't been resolved. Before creating the document for "AMP JS errors", there'd be some investigation needed to determine if there are other AMP JS errors we should document as well.
this creates a huge number of 404 on the webserver logs, is this really necessary?
@aghassemi - see comment above.
Any way to disable this ? its filling our logs with 404s.
@nainar are you able to provide any insight on this issue? Is this still happening? I'm unsure where it would be documented.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Most helpful comment
Any way to disable this ? its filling our logs with 404s.