Repository navigation
name who is sending the 403 - #2801
Merged
Merged
Conversation
Flotapponnier
force-pushed
the
fix/birdeye-403-source
branch
from
October 4, 2026 13:32
8d0170f to
5953a24
Compare
Two assumptions I never checked, and one of them is probably the answer. getProxyDialer sets Proxy only when url.Parse succeeds and drops it in SILENCE otherwise, so a malformed value dials direct and looks exactly like a refused proxy. The startup line added earlier proves the VARIABLE exists; it proves nothing about whether this dialer carries it. Two different facts, and I treated them as one. And a proxy refusing an unauthorised source IP and an edge refusing a datacenter both surface through gorilla as the same bad handshake 403. Everything else is eliminated by measurement: the same proxy URL read out of Railway connects from a laptop; three dialer shapes including getProxyDialer's exact one all connect; getProxyDialer() is called; the container reports the variable at the same 52 chars that work here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Flotapponnier
force-pushed
the
fix/birdeye-403-source
branch
from
October 4, 2026 13:40
5953a24 to
e5970e8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have assumed Cloudflare all afternoon without checking. A proxy that refuses an unauthorised source IP and an edge that refuses a datacenter both surface through gorilla as the same
bad handshake 403.Everything else is now eliminated by measurement:
getProxyDialer()is called, line 198proxy configured (52 chars), the same length as the one that worksSo the dial is right, the proxy is right, the code is right, and the refusal is still there.
Cloudflare stamps
ServerandCf-Ray; a proxy rejecting a source sends neither. One log line settles which, and nothing short of it will.Checks
go build ./...andgo test ./cmd/script/clean🤖 Generated with Claude Code