Skip to content

feat: add proxy fallback for links that return 403 - #554

Closed
shrwnsan wants to merge 1 commit into
tcort:masterfrom
shrwnsan:feature/proxy-fallback
Closed

feat: add proxy fallback for links that return 403#554
shrwnsan wants to merge 1 commit into
tcort:masterfrom
shrwnsan:feature/proxy-fallback

Conversation

@shrwnsan

Copy link
Copy Markdown

When a link returns 403 (or other configurable status codes), retry the check through a chain of proxy services to validate accessibility.

Features:

  • Default proxy chain: r.jina.ai → corsproxy.io → allorigins
  • Configurable via fallbackProxies option
  • Configurable status codes via fallbackForCodes option (default: [403])
  • Shows which proxy was used when validation succeeds

This solves the issue where legitimate URLs (like claude.ai, perplexity.ai) block automated access but work fine for human users.

Related issues: #285, #201

Amp-Thread-ID: https://ampcode.com/threads/T-019c0cc3-3007-77c9-bbae-4a912d68fd96

When a link returns 403 (or other configurable status codes), retry
the check through a chain of proxy services to validate accessibility.

Features:
- Default proxy chain: r.jina.ai → corsproxy.io → allorigins
- Configurable via `fallbackProxies` option
- Configurable status codes via `fallbackForCodes` option (default: [403])
- Shows which proxy was used when validation succeeds

This solves the issue where legitimate URLs (like claude.ai, perplexity.ai)
block automated access but work fine for human users.

Related issues: tcort#285, tcort#201

Co-authored-by: GLM <zai-org@users.noreply.github.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019c0cc3-3007-77c9-bbae-4a912d68fd96
Co-authored-by: Amp <amp@ampcode.com>
@github-actions

Copy link
Copy Markdown

This pull request has been marked as stale because it has been open 60 days with no activity. It will be closed in 90 days unless the stale label is removed or someone adds a comment.

@github-actions github-actions Bot added the Stale label Apr 30, 2026
@tcort

tcort commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Definitely not. We're not hard coding three random proxy URLs in the source. If you're experiencing 403s, the solution is to talk to the site operator to see why your activity is forbidden and adjust accordingly not try to circumvent restrictions.

@tcort tcort closed this Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants