wreq
Fetch pages with browser-like network fingerprints, without launching a browser.
29 September 2026 · no proxy
Two public pages with wreq 0.12.3
A direct request returned usable Wikipedia article content (HTTP 200). Amazon laptop search returned its “Sorry! Something went wrong!” page (HTTP 503), with no product results. These two attempts are a small inventory check, not a success rate or evidence of why Amazon failed.
Wikipedia: run metadata · raw response · resource use
Amazon: run metadata · raw response · resource use
Published test history
These May 2026 runs used one network without a proxy. Their pass counts describe those older attempts, not how the tool will perform today.
| Mode | Date | Version | Observed result | Network |
|---|---|---|---|---|
| wreq | 2026-05-24 | 0.11.3 | 2/21 required-content checks | No proxy |
Where it fits
When curl_cffi's profiles don't fit and you can invest in tuning request shape per target — its fingerprint demonstrably reaches places others can't, but expect to debug defaults.
This guidance comes from the May 2026 review. Check a recent run before choosing for production.
What it can do
- Use a proxy
- Fetch HTML
Capabilities are catalog notes, not outcomes from the benchmark above.
Project record
- Type
- Fetch pages
- Ecosystem
- python
- Repo check
- 2026-05-23
- License
- Apache-2.0
Repository metadata is a dated snapshot, not a live health guarantee.
See how we validate pages, including what a pass does and does not mean.