dgtlmoon / dgtlmoon/changedetection.io
[feature] Proxy fallback / fall-through on 4xx errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 2.1k
- Avg merge
- 22h 52m
- Merged PRs (30d)
- 70
Description
When a 4xx error is received, would be nice to set some priority mapping (or 'random') to make it skip to different proxies to keep trying access
- plus some config field in the proxy json list file for a message like for example "403 was found, so switched to a different proxy"
- also in the ui config
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing proxy selection and the handling of 4xx responses, then inspect the proxy JSON list configuration and the UI configuration mentioned in the issue. The work is done when the configured fallback behavior, priority or random selection, and user-facing switch message are defined and covered for both configuration surfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100