Sample
Distinguish reqwest Policy::none from Policy::limited(0), and inspect the initial URL through RedirectAttempt::previous in a custom redirect policy
sha256:bf92f0d351b495dfbadfc1a4ce84ae932a05d9fc4e91c83ca0c1b27ac870730e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Distinguish reqwest Policy::none from Policy::limited(0), and inspect the initial URL through RedirectAttempt::previous in a custom redirect policy HOW
- Packages
- reqwest 0.13.4 tokio 1.53.1
- Environment
- rust
- Created
- 2026-08-17T01:07:24Z
Commonly assumed
Policy::limited(0) is equivalent to Policy::none(), and a custom redirect attempt's previous list excludes the initial request URL.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Policy::none returns the original 302 response without treating the redirect as an error
- Policy::limited(0) rejects the first 302 response with an error for which is_redirect returns true
- On the first redirect, RedirectAttempt::previous contains exactly the initial request URL
- A custom policy can follow the redirect and receive the final 200 response while observing the initial URL in previous
Files
- Cargo.lock
- Cargo.toml
- csx.json
- src/lib.rs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- rust 1 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · cargo@1 · 2026-08-17 · ed25519:d91480838ac982c9