davsclaus commented on issue #1631: URL: https://github.com/apache/camel-website/issues/1631#issuecomment-4683903540
## First deploy with rsync (#1633) — results The first build with the rsync deploy produced a diff of **30 files** instead of the previous ~14,000. The PURGE event fired successfully. ### Before and after | | Before #1633 | After #1633 | |---|---|---| | Deploy diff | ~14,000 files (every file) | 30 files (only actual changes) | | PURGE payload | >256KB (silently dropped) | Tiny (fires successfully) | ### Proof: cached 404s cleared for changed files We touched 2 blog posts that had cached 404s. After the deploy: ``` OK 200 blog/2026/06/camel-by-the-numbers/ ← was 404, touched in source, now fixed OK 200 blog/2026/05/camel-quarkus-3.33.1/ ← was 404, touched in source, now fixed FAIL 404 blog/2026/05/RELEASE-4.14.5/ ← still 404, not in the 30-file diff FAIL 404 blog/2026/05/RELEASE-4.18.3/ ← still 404, not in the 30-file diff FAIL 404 blog/2026/05/RELEASE-4.20.1/ ← still 404, not in the 30-file diff FAIL 404 manual/faq.html ← still 404, not in the 30-file diff FAIL 404 manual/enterprise-integration-patterns.html ← still 404, not in the 30-file diff FAIL 404 releases/release-4.18.3/ ← still 404, not in the 30-file diff ``` **Pages that changed in the deploy diff → PURGE fired → cached 404 cleared → working again.** **Pages that didn't change → no PURGE → cached 404 persists until TTL expires.** This confirms the rsync deploy works as intended. But cached 404s from before the fix will linger until their CDN TTL expires. The only permanent fix is the INFRA VCL change to stop Fastly from caching 404 responses. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
