Project: easygoing-creativity (ID: 83e3f1cf-4637-4f47-8803-46527ec8dca6) Service: web (ID: f2627244-d345-4a89-956e-253cda6dec01) Custom domain: quotepazze.com Issue: The Railway Edge CDN is serving a 4-day-old cached HTML response for quotepazze.com/ and quotepazze.com/bonus-benvenuto. The cached version is from May 13, 2026 and does NOT include a legally mandatory compliance link (Italian law Art. 7 DL 87/2018 requires a link to ADM gambling authority on all pages). Evidence: - Response header: date: Wed, 13 May 2026 09:59:54 GMT (4+ days old) - Response header: server: railway-edge - Response header: x-railway-edge: railway/europe-west4-drams3a - The HTML body references home-app.d9760183.js (old build hash — current code has a different hash) - The ADM compliance link (gioco_dist_note) is missing from the served HTML but IS present in the current git repo and deployed code - /api/fixtures on the same service returns today's date correctly — only the HTML pages are stuck in cache Attempts to purge that failed: - Multiple redeployments via Railway dashboard and GraphQL API (deploymentRedeploy) - Added Cache-Control: no-store, must-revalidate + Surrogate-Control: no-store headers to origin - Custom domain delete + recreate (domain ID: 0f50fe20-33ef-408d-97f2-27e8cecf5d4b) Per the CDN disable announcement (3 days ago), the CDN should be disabled — but the edge node europe-west4-drams3a is still serving the May 13 cached response. Request: Please manually purge the edge cache for: - quotepazze.com/ - quotepazze.com/bonus-benvenuto This is urgent due to the legal compliance requirement.

Edge CDN serving stale cached HTML from May 13 despite CDN disable announcement

gallo93

HOBBYOP

5 days ago

Project: easygoing-creativity (ID: 83e3f1cf-4637-4f47-8803-46527ec8dca6)

Service: web (ID: f2627244-d345-4a89-956e-253cda6dec01)

Custom domain: quotepazze.com

Issue: The Railway Edge CDN is serving a 4-day-old cached HTML response for quotepazze.com/ and quotepazze.com/bonus-benvenuto. The cached version is from May 13, 2026 and does NOT include a legally mandatory compliance link (Italian law Art. 7 DL 87/2018 requires a link to ADM gambling authority on all pages).

Evidence:

Response header: date: Wed, 13 May 2026 09:59:54 GMT (4+ days old)
Response header: server: railway-edge
Response header: x-railway-edge: railway/europe-west4-drams3a
The HTML body references home-app.d9760183.js (old build hash — current code has a different hash)
The ADM compliance link (gioco_dist_note) is missing from the served HTML but IS present in the current git repo and deployed code
/api/fixtures on the same service returns today's date correctly — only the HTML pages are stuck in cache

Attempts to purge that failed:

Multiple redeployments via Railway dashboard and GraphQL API (deploymentRedeploy)
Added Cache-Control: no-store, must-revalidate + Surrogate-Control: no-store headers to origin
Custom domain delete + recreate (domain ID: 0f50fe20-33ef-408d-97f2-27e8cecf5d4b)

Per the CDN disable announcement (3 days ago), the CDN should be disabled — but the edge node europe-west4-drams3a is still serving the May 13 cached response.

Request: Please manually purge the edge cache for:

quotepazze.com/
quotepazze.com/bonus-benvenuto

This is urgent due to the legal compliance requirement.

$10 Bounty

3 Replies

Status changed to Awaiting Railway Response Railway • 5 days ago

Status changed to Open Railway • 5 days ago

yellowmacaroni

PRO

5 days ago

It doesn't seem to be serving the cached content for me nor is it showing the cache headers from railway. Either way, you can use the HTTP PURGE method (curl -X PURGE (url)) to purge a single asset.

gyanavkhandelwal6396-cmyk

FREE

5 days ago

This is almost certainly a stale Railway Edge CDN cache serving an old static HTML artifact, not a deployment issue: your API responses are fresh, the origin code contains the ADM link, but the edge is still returning a May 13 build (home-app.d9760183.js) from railway/europe-west4-drams3a.

Because redeploys, Cache-Control: no-store, and domain reattachment did not invalidate the cached HTML, the remaining fix is a platform-side edge purge/invalidation for quotepazze.com/ and /bonus-benvenuto; as a temporary mitigation, you can also bypass the stale cache by attaching a new subdomain or changing the asset/build hash so the edge fetches a fresh origin response immediately

phin

EMPLOYEE

4 days ago

This isn't possible, as the CDN functionality is currently disabled. Your domain's DNS points to an address which bypasses the caching layer. If the caching was enabled then you'd see an x-cache header.

Welcome!