4 comments (4 comments)2 reactions (2 reactions)0 assignees (0 assignees)Rust84,934 stars (84,934 stars)3,111 forks (3,111 forks)batch import
bughelp wanted
Description
e.g., https://github.com/astral-sh/uv/issues/16233
We should not be retrying that failed request.
Contributor guide
- Tech stack
- rust
- Domain
- securityapi
- Issue type
- bug
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- fresh
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- basic Rustunderstanding of HTTP retry logic
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- The issue requests that SSL certificate errors should not be retried when making HTTP requests. Start by locating the retry logic in the codebase, likely in the HTTP client module (e.g., src/**/http.rs or similar). Look for where errors are caught and retries are triggered. Identify how SSL errors are represented (e.g., via the `rustls` or `native tls` crate) and ensure that such errors skip the retry loop. No linked PRs exist; refer to the referenced issue ( #16233 ) for context. After implementing, verify that the behavior matches expectations by simulating an SSL error.