Repository navigation
Confirm the Proxy Headers Before Calling a Run Proxied - #498
Conversation
After a hostname flips to proxied, the local resolver kept answering with the origin for minutes, so a live check in that window measures the origin rather than Cloudflare. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
A recorded local strict-review pass covers head |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #498 +/- ##
========================================
Coverage 49.70% 49.70%
========================================
Files 10 10
Lines 3058 3058
========================================
Hits 1520 1520
Misses 1538 1538
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
🔵 Needs a closer look
The documented probe must be corrected to use the same curl configuration behavior as the checker and to require both proxy headers.
No open issues 🎉
What changed in this PR
This documentation-only PR adds a Cloudflare proxy verification step before running hand-checked production URL checks.
Changes:
- Documents the required
server: cloudflareandcf-rayresponse headers. - Adds a same-machine
curlprobe before the live URL check. - Explains resolver-cache delays after proxy changes.
| File | Summary |
|---|---|
OPERATIONS.md |
Adds Cloudflare proxy-header confirmation guidance; the probe should also ignore local curl configuration and independently require both headers. |
Review effort: Lite
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
A recorded local strict-review pass covers head |
|
Answering the round on 079ba9f, "use the same curl configuration behavior as the checker and require both proxy headers":
|
Summary
A hand run of
checks/check-live-urls.shcounts as measured through Cloudflare only once the target answersserver: cloudflarewith acf-rayheader. Right after a hostname flips to proxied, the resolver on the machine running the check can keep answering with the origin for minutes. This happened after both production flips. OPERATIONS.md "Deploying" now says to read those headers from the same machine before the run, and gives the command.This is step 1 of handoff #493. It is docs only and needs no release of its own.
Verification
curl -sSI ... | grep -iE '^(server|cf-ray):'printed both headers against production.prose_lint.py --diffand itssentence-lengthcheck are clean.Local review
The local strict pass ran twice. The first raised two
introducedfindings on the new paragraph: it credited DNS over HTTPS rather than a different resolver cache, and it was not scoped to a hand run on the checking machine. Both were fixed in 079ba9f, and the second pass found nothing.🤖 Generated with Claude Code