Single-file cache purging not working

Website, Application, Performance
1

There was a problem with purging single pages yesterday.

However, I am still unable to purge single pages. Is there any action I can take to resolve the issue?

3 Likes
2

Same thing is happening to me… Don’t know what to do.

3

Why is the content of this file different?

curl https://osp-assets.pn.vg/37f77b04-2931-461c-bd78-536a0a68bc20.json

VS

curl -H 'Origin: https://www.otvfoco.com.br' "https://osp-assets.pn.vg/37f77b04-2931-461c-bd78-536a0a68bc20.json"

This is happening since yesterday. If I access a cached URL without passing the “origin” header, I get the proper version of the asset. But if I pass an “origin” header I get the old version of the file.

Please note that I have purged the cache for that specific origin!

Can anyone help me on this or tell me how can I get this message to anyone at Cloudflare?

4

Same problem for me. Also confirmed by some users on a Wordpress support forum this morning. The only fix is a full purge, which is quite inconvenient. I’m waiting to see an incident notice on the Cloudflare Status page.

1 Like
5

The Origin request header forms part of the cache key. When purging assets which use an Origin header you need to use the API, and pass the Origin header value along with the URL. The API documentation gives an example that you can follow.

6

Yes, I am aware of that @michael. Here’s how I am purging the cache via the API:

{
	"files": 
	[
		"https://osp-assets.pn.vg/37f77b04-2931-461c-bd78-536a0a68bc20.json",
		{
			"url": "https://osp-assets.pn.vg/37f77b04-2931-461c-bd78-536a0a68bc20.json",
			"headers": {
				"Origin": "https://www.otvfoco.com.br"
			}
		}
	]
}

The problem is that when I access the URL passing the origin, I get the old file.

7

This problem was still not fixed and Cloudflare is not recognizing the issue. I don’t have access to direct support and this is hurting my business quite a lot. Can someone with access to support make them aware of this? Simply put:

– The issue of June 28th is still not fixed.

8

I can confirm too that the issue is not fixed.

But a Wordpress user notified me that he has created a support ticket. I can’t access it because I’m on a free account like you Tiago, but here is the link if it helps: https://support.cloudflare.com/hc/en-us/requests/2196125

9

I just sent a support request, Tiago.

https://support.cloudflare.com/hc/en-us/requests/2196198

Hopefully, I can get the attention of @MoreHelp to look at the issue. I have checked my log files and it shows “success”: true, when I purge a page. But it is not replacing the page with a fresh version from the origin server.

If you want to send a request, go to this page: https://dash.cloudflare.com/d5999d6d2d13e1a16de07cd5dfcefb07/support

Scroll down to the last option, and click Get More Help. You can send your request from there.

1 Like
10

I’ve escalated this issue for the attention of the customer support team, hopefully they will get back to you soon.

3 Likes
11

Thanks, domjh - Hopefully, they will.

1 Like
12

Hi there,

This was escalated to us by @domjh

I’m not aware of any incidents related to purge delays ongoing from the incident on the 28th - looking at the graphs internally that we use to monitor, I can see there has been some periods where it was increased time to purge - but overall I’m not seeing an increase.

Based on the updates in the thread there could be a number of different reasons.

I see mentions of origin headers, wordpress (APO) - there could be a couple of things coming into play here.

@derekhaines I will respond via your support ticket

@tiago.carvalho Do you have the output of osp-assets.pn.vg/cdn/cgi/trace (censor your client IP) and a copy of the request/response headers for that file that is not purging?

3 Likes
13

Hi @Damian,

Since the problem is happening in all my domains I’ll be using an example from “cdn.pn.vg” instead of “osp-assets.pn.vg”

Here’s the output of https://cdn.pn.vg/cdn-cgi/trace (but please note that this problem is affecting other regions – by business is mostly in Brazil and the cache is not purged there also):

fl=107f61
h=cdn.pn.vg
ip=[REMOVED]
ts=1625063831.609
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
colo=LIS
http=http/3
loc=PT
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

And here’s a sample file that is not purging: https://cdn.pn.vg/sites/20956218-f85a-443f-a178-8e067c3a0c1d.js

My request:

curl 'https://cdn.pn.vg/sites/20956218-f85a-443f-a178-8e067c3a0c1d.js' \
  -H 'authority: cdn.pn.vg' \
  -H 'pragma: no-cache' \
  -H 'cache-control: no-cache' \
  -H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'upgrade-insecure-requests: 1' \
  -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36' \
  -H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9' \
  -H 'sec-fetch-site: none' \
  -H 'sec-fetch-mode: navigate' \
  -H 'sec-fetch-user: ?1' \
  -H 'sec-fetch-dest: document' \
  -H 'accept-language: en-GB,en-US;q=0.9,en;q=0.8,pt;q=0.7,fr;q=0.6' \
  -H 'cookie: __cf_bm=e32a9dce3f622e91130f1c9632f2a0774656d2f4-1625062767-1800-AX7CBeG+hib/ONu1OmIM5pncm6I1wzfluOQreqMPMq9Fs1+dFuYSc9O+ZMQhcgclm03hs0e18T5hAGsxCJtJTZg=' \
  --compressed

The response Headers:

age: 430
alt-svc: h3-27=":443"; ma=86400, h3-28=":443"; ma=86400, h3-29=":443"; ma=86400, h3=":443"; ma=86400
cache-control: max-age=14400
cf-cache-status: HIT
cf-ray: 6678163cb98053b0-LHR
cf-request-id: 0afeec39f5000053b0ff324000000001
content-encoding: br
content-type: text/javascript
date: Wed, 30 Jun 2021 14:29:27 GMT
etag: W/"ecb53d6022e9a62c546735da5d059052"
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
last-modified: Wed, 30 Jun 2021 14:21:35 GMT
nel: {"report_to":"cf-nel","max_age":604800}
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v2?s=AdXo0ppSKnr9KkRA1RAWBH6y4ioe1cHaeWpa2HJ%2F8JAQ0Mt5Gvt9NnYX0Uck09NYZ9FTwbLkAwyvLQeUuc2j6vLXcgCLZrGOvBli25qt7v5b0Zhm%2F%2Fk4"}],"group":"cf-nel","max_age":604800}
server: cloudflare
vary: Accept-Encoding
via: 1.1 f6a44ee9a38356c53cc0c2455e4126f7.cloudfront.net (CloudFront)
x-amz-cf-id: jODjtwYX5q3Eunb1uj1nQOrOjRUy1PAE1uSxSk8prQBtjj9SDSezuw==
x-amz-cf-pop: LHR52-C1
x-cache: Miss from cloudfront

The returned body:

(function(p,u,s,h,n,e,w,z){p[n]=z;p[h]=p[h]||[];p[h].push(["init",z]);var f=u.getElementsByTagName(s)[0],j=u.createElement(s);j.async=w;j.src=e;f.parentNode.insertBefore(j,f)})(window,document,'script','IlabsPush','_ilabsPushConfig','https://cdn.pn.vg/push/ilabspush.min.js',!0,{"optin":{"mailinglistOsp":{"status":!0,"activation":{"type":"optinClickNo"},"title":"Prefere assinar nossa Newsletter?","subtitle":"Ao continuar voc\u00ea declara que leu e assinou nossos Termos e Condi\u00e7\u00f5es","buttonSignUp":"OK","thankYou":"Obrigado pelo cadastro :)"},"native":!0,"activation":{"type":"auto"},"%desktopImage%":"https:\/\/icons.pushnews.eu\/default_images\/pushnews-pushicon-128-red.png","%desktopTxtTitle%":"Fique ligado!","%desktopTxtBody%":"Receba conte\u00fados exclusivos para voc\u00ea!","%desktopTxtButtonNo%":"N\u00e3o, obrigado","%desktopTxtButtonYes%":"Eba, quero!","nativePrePrompt":!1,"theme":"https"},"popup":{"emailCapture":!0,"emailActionMessage":"Quer tamb\u00e9m se inscrever na nossa newsletter?","emailSubtitleMessage":"Ao continuar voc\u00ea declara que leu e concordou com nossos Termos e Condi\u00e7\u00f5es","emailButtonSubmit":"Assinar","emailSuccessMessage":"Obrigado pelo cadastro :)","emailNoThanks":"N\u00e3o, obrigado.","name":"5a31fb1653f0 ngrok io","domain":"5a31fb1653f0.ngrok.io","appId":"20956218-f85a-443f-a178-8e067c3a0c1d","actionMessage":"quer te enviar notifica\u00e7\u00f5es:","notificationIcon":"https:\/\/icons.pushnews.eu\/default_images\/pushnews-pushicon-128-red.png","notificationTitle":"Exemplo","notificationMessage":"Esta \u00e9 uma notifica\u00e7\u00e3o exemplo","caption":"(pode cancelar quando quiser)"},"osp":{"status":!0,"activation":{"type":"scroll"},"trackViews":!0,"trackClicks":!0},"extra":{"googleAnalytics":{"events":[]},"api":{"url":"https:\/\/api.pushnews.eu","publicToken":"pub_154d45a94d6325d82bb04ee2a21a8381a397644a9a51"},"constants":{"ONESIGNAL_SDK_URL":"https:\/\/api.pn.vg\/sdks\/OneSignalSDK.js"}}})

The problem:

  • This is not the newest version of the file
  • I have purged the URL after changing the file but it remains the same – the cache is not being purged for this file

This is the newest content of that file:

(function(p,u,s,h,n,e,w,z){p[n]=z;p[h]=p[h]||[];p[h].push(["init",z]);var f=u.getElementsByTagName(s)[0],j=u.createElement(s);j.async=w;j.src=e;f.parentNode.insertBefore(j,f)})(window,document,'script','IlabsPush','_ilabsPushConfig','https://cdn.pn.vg/push/ilabspush.min.js',!0,{"optin":{"mailinglistOsp":{"status":!0,"activation":{"type":"optinClickNo"},"title":"Prefere assinar nossa Newsletter?","subtitle":"Ao continuar voc\u00ea declara que leu e assinou nossos Termos e Condi\u00e7\u00f5es","buttonSignUp":"OK","thankYou":"Obrigado pelo cadastro :)"},"native":!0,"activation":{"type":"auto"},"%desktopImage%":"https:\/\/icons.pushnews.eu\/default_images\/pushnews-pushicon-128-red.png","%desktopTxtTitle%":"Fique ligado!","%desktopTxtBody%":"Receba conte\u00fados exclusivos para voc\u00ea!","%desktopTxtButtonNo%":"N\u00e3o, obrigado","%desktopTxtButtonYes%":"Eba, quero!","nativePrePrompt":!1,"theme":"https"},"popup":{"emailCapture":!0,"emailActionMessage":"Quer tamb\u00e9m se inscrever na nossa newsletter?","emailSubtitleMessage":"Ao continuar voc\u00ea declara que leu e concordou com nossos Termos e Condi\u00e7\u00f5es","emailButtonSubmit":"Assinar","emailSuccessMessage":"Obrigado pelo cadastro :)","emailNoThanks":"N\u00e3o, obrigado.","name":"5a31fb1653f0 ngrok io","domain":"5a31fb1653f0.ngrok.io","appId":"20956218-f85a-443f-a178-8e067c3a0c1d","actionMessage":"quer te enviar notifica\u00e7\u00f5es:","notificationIcon":"https:\/\/icons.pushnews.eu\/default_images\/pushnews-pushicon-128-red.png","notificationTitle":"Exemplo","notificationMessage":"Esta \u00e9 uma notifica\u00e7\u00e3o exemplo","caption":"(pode cancelar quando quiser)"},"osp":{"status":!0,"activation":{"type":"auto"},"trackViews":!0,"trackClicks":!0},"extra":{"googleAnalytics":{"events":[]},"api":{"url":"https:\/\/api.pushnews.eu","publicToken":"pub_154d45a94d6325d82bb04ee2a21a8381a397644a9a51"},"constants":{"ONESIGNAL_SDK_URL":"https:\/\/api.pn.vg\/sdks\/OneSignalSDK.js"}}})

(I know the difference is small, but if you search for the word “scroll” it is not being used on the newer asset yet it was used on the original file’s content).

Can I provide you with more debugging information?

Thanks a lot in advance!

14

Further explaining the problem. It seems to also be a region problem.

I am testing thins command:

curl 'https://cdn.pn.vg/sites/20956218-f85a-443f-a178-8e067c3a0c1d.js' | grep scroll
  • :x: From MY location (Portugal), the word “scroll” is present on the file body – this is not suppposed.
  • :white_check_mark: From Brasil, the word “scroll” is not present – perfect! This means the newest file is being served.

Here’s MY location cgi-bin/trace (receiving old content :x:):

fl=21f524
h=cdn.pn.vg
ip=[PORTUGUESE_IP_ADDRESS]
ts=1625065170.563
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
colo=LHR
http=http/3
loc=PT
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

And here’s a cgi-bin/trace output from a colleague at Brasil (Receiving GOOD and updated content :white_check_mark:):

fl=11f365
h=cdn.pn.vg
ip=[BRAZILIAN_IP_ADDRESS]
ts=1625065183.323
visit_scheme=https
uag=Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
colo=EWR
http=http/2
loc=BR
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
1 Like
15

I am issues having issues with the homepage not updating on Wordpress. I am using the official Wordpress plug-in. Purging the cache from cloudflare admin is the only way to fix the problem.

I suspect my issue is related to the issue other Wordpress users are reporting.

16

I am not able to clear cache using Dashboard of Cloudflare too., Please fix the issue thank you.

17

Same situations with my site. I use cache all page rule and custom plugin for clearing cache with every change i make on site but since yesterday it don’t work and my only option is to clear full cache though cloudflare page.

18

I’m experiencing the same issue. No code changes on my side and suddenly the single page purge does not work although the purge request does return a 2xx HTTP response code.

19

Yes I am facing too.

20

Hi,
I’m experiencing the same issue. I haven’t changed anything and single page purge is not working anymore. I opened a support ticket, it has been marked as solved but I’m still experiencing the issue