Amphtml: Amp cache purge API issue

[santoshkjena]

We are using AMP cache purge API from google to purge any URL from google amp cdn but this is not working .
Below is the code showing the way we are executing the API .
Code here
Please find the curl command screenshot (showing the response headers and body) link below
screenshot here
Need your quick help to get this verified, if we are missing anything.

[vishalitg]

I'm also facing the same issue. Please, help me to fix this issue.

[aghassemi]

@santoshkjena Thanks for the report, is this something that used to work with the same code or is the code new?

/to @jgluk to triage.
/cc @Gregable

[Gregable]

Tracked internally for Google's Cache as 122836254

[Gregable]

@santoshkjena - can you share the amp cache URLs with me? If you don't want to share them on github, you can send me a private message on our slack channel. My user name there is also gregable.

[santoshkjena]

@aghassemi This is a new implementation and it is implemented as per the steps defined on this https://developers.google.com/amp/cache/update-cache URL

[santoshkjena]

@Gregable i have sent you the details on slack . please have a look.

[rudygalfi]

@Gregable Did this get resolved over Slack?

[Gregable]

The details sent over slack were shared with the Google Cache team. The issue was not resolved to the best of my knowledge.

[Antoinebr]

I'm facing the same issue.

The API sends back : OK but the cache is not flushed.

My canonical page has a cache-control: max-age=0

To test how fresh is the cached version I echo a timestamp ( server side ) on my canonical page and compare it to the cached page.

The code I used to flush the cache : https://glitch.com/edit/#!/amp-tracking?path=bustCache.js:40:13

I recorded a video which shows the issue :

https://www.youtube.com/watch?v=MiozEjLLWSk&feature=youtu.be

@Googlers :

Related internal issues :

122836254
110992715
110364829

[morsssss]

@jgluk does this API work at all currently? Or is it failing in certain circumstances?

[jgluk]

We are currently internally tracking a project to fix some of the inconsistent behavior of this API.

[morsssss]

thanks! glad to hear it 👍

[stale[bot]]

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.