Abc jili download free android.Enjoy Free 888+200 Daily Legal Bonus

Resolved Managedserver.it
(@dreamsnet)

2 years, 12 months ago

Hi,

we start today to debug customer website using Varnish Cache correctly, and i look when some post is updated the W3TC plugin (with amp extension enabled) send PURGE command for the main post article, and the amp url, using /amp suffix.

When i check the /amp url using linux utility curl -I https://www.spazionapoli.it/2021/12/01/sassuolo-napoli-ferrari/amp i look a 301 redirect to https://www.spazionapoli.it/2021/12/01/sassuolo-napoli-ferrari/amp/ (with the / in the end).

If i repeat the operation doing curl -I https://www.spazionapoli.it/2021/12/01/sassuolo-napoli-ferrari/amp/ i see Varnish cache not purge.

I investigate on this and i think the amp suffix in the amp extension configuration is wrong by default.

Can u check this and solve in the future W3 Total Cache version ?

Best Regards

The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)

Thread Starter Managedserver.it
(@dreamsnet)

2 years, 12 months ago

I solve the problem adding amp/ to amp extension setup, but i suppose the amp standard default is wrong and need to be fix in the future release, or plugin need to call double PURGE command : one for /amp and one for amp/ (with the slash in the end).

Plugin Contributor Marko Vasiljevic
(@vmarko)

2 years, 12 months ago

Hello @dreamsnet

Thank you for reaching out and for the information provided.
Can you please share which AMP plugin is used in this case?
To confirm, you added amp/ to Performance>Extensions>AMP>AMP URL Postfix: ?
The default for the AMP plugin should be ?amp or /amp/
Thanks!
Thread Starter Managedserver.it
(@dreamsnet)

2 years, 11 months ago
Hi,

we use : AMP for WP – Accelerated Mobile Pages for WordPress – Versione 1.0.77.20

But W3 Total Cache in the AMP extension use “amp” in the suffix.

Example : https://website.tld/post/amp

I grep the access.log after update post and i see PURGE command to /amp suffix and not /amp/
```
127.0.0.1 - - [02/Dec/2021:13:25:29 +0100] "PURGE /page/2/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:29 +0100] "PURGE /page/3/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:29 +0100] "PURGE /page/4/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:29 +0100] "PURGE /page/5/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:30 +0100] "PURGE /page/6/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:30 +0100] "PURGE /page/7/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:30 +0100] "PURGE /page/8/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
127.0.0.1 - - [02/Dec/2021:13:25:30 +0100] "PURGE /page/9/amp HTTP/1.1" 301 5 "-" "W3 Total Cache"
```
If i check the header after purge i see the Age of Varnish cache at /amp/ url not expired.

Im pretty sure amp is ok only if the application logic of W3TC add / in the end.

I solve the problem change the suffix from amp to amp/ in the configuration for AMP W3TC extension.
- This reply was modified 2 years, 11 months ago by Managedserver.it.
Plugin Contributor Marko Vasiljevic
(@vmarko)

2 years, 11 months ago

Hello @dreamsnet

Thank you for the information.
I am glad to know that the problem is fixed after you added amp/ in the Performance>Extensions>AMP>AMP URL Postfix:
This is why the option AMP URL Postfix: is added.
We’ll make sure to check potential compatibility issues and possibly add more options for this.
Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Amp cache PURGE : amp different from amp/ (slash in the end)’ is closed to new replies.