This is about the PCS JS endpoint: https://meta.wikimedia.org/api/rest_v1/data/javascript/mobile/pcs. (Others could be affected as well.)
I deployed PCS today (4/2/2020) and purged the PCS JS endpoint (plus a few others) using mwmaint1002:
echo 'https://meta.wikimedia.org/api/rest_v1/data/javascript/mobile/pcs' | mwscript purgeList.php
While I personally can see the update in my location, one of my colleagues on the east coast doesn't.
Here are the cache related headers for this:
Central US (response is up-to-date):
cache-control: public, max-age=86400, s-maxage=86400 date: Thu, 02 Apr 2020 22:07:29 GMT content-location: https://meta.wikimedia.org/api/rest_v1/data/javascript/mobile/pcs x-request-id: d91de138-dc64-4d34-adb8-cd89084990ea server: restbase2011 etag: W/"-220997356691/57fdfcf0-752e-11ea-9b92-ae2ab0d75385" age: 1694 x-cache: cp2035 hit, cp2027 hit/7 x-cache-status: hit-front server-timing: cache;desc="hit-front" strict-transport-security: max-age=106384710; includeSubDomains; preload set-cookie: WMF-Last-Access=02-Apr-2020;Path=/;HttpOnly;secure;Expires=Mon, 04 May 2020 12:00:00 GMT
East coast US (response is old):
Age: 79169 X-Cache: cp1075 hit, cp1083 hit/415 Content-Type: text/javascript; charset=utf-8; profile="https://www.mediawiki.org/wiki/Specs/JavaScript/1.0.0" Etag: W/"-524204942720/cad13560-7477-11ea-8ee4-c76a18c093f5" x-webkit-csp: default-src 'none'; frame-ancestors 'none' x-content-type-options: nosniff X-Cache-Status: hit-front
Note the age is much higher in the second response. Is there anything we should do differently to purge this from Varnish?