austinnovelty

So I didnt get a chance to reply (because weekend).

I’ve had issues when attempting to clear cache.

With Bing/Cloudflare I can purge the amp url with a uri encoded querystring ‘%3famp’ or ‘%3Famp’.
With google’s amp cache I have to use the upper case version or I get errors returned. I am also able to add the ‘amp’ parameter after the amp_ts parameter when attempting to ‘purge’ a url from google’s cache. With the latter I only have to reorder the querystring no encoding. This method did not work with Bing/Cloudflare however.

So while the ampbench tool may need a fix, it seems that each cache purge behaviour is different as well.

Again, I am not saying ‘?amp’ isn’t correct to implement, It does seem to expose issues with other AMP service functionality.

I asked because the github page clearly says AMP HTML Validator. https://github.com/ampproject/amphtml/blob/master/validator/README.md

It does not mention that it checks the URL of the site as far as I have seen.

Does the Validator link you posted check Syntax only? or does it actually inspect the url?

done. https://www.ads-software.com/support/topic/amp-querystring-vs-amp-in-path/

I created a wordpress account just for this post.

@westonruter Why would you ignore the original post’s link to an accepted validation tool that is linked to in AMP Project docs? https://amp.dev/documentation/guides-and-tutorials/learn/amp-caches-and-cors/amp-cache-debugging?format=websites

Your AMP HTML syntax is valid, but the url generation seems to cause issues.

AMPbench fails on the querystring ‘?amp’ as far as I can tell. There isn’t much in terms of documentation but using ‘?amp’ causes issues with purging caches.

https://ampbench.appspot.com/validate?url=https%3A%2F%2Fwww.history101.com%2Fvikingfacts%2F%3Famp

If you look at any mainstream site that has amp implemented, they us either a subdomain, directory in the path, or some combination of the two. Your implementation is the first i’ve seen that uses a query string.

The first issue I ran into was when I attempted to purge the amp cache. I had to use the work around listed in:
https://github.com/ampproject/amphtml/issues/10883

which worked fine for Google’s amp cache but not cloudflare or bing.

Due to lack of documentation in regards to the AMP URL structure, I can see how this issue occurred. One can argue that the issue is with the AMP Cache code, but why go against the examples in their docs?