You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Enhance proxy usage documentation with the correct usage.
Expanded the proxy usage documentation to include authentication, per-request proxies with custom headers, and clarified Unix socket proxy usage.
* Revise proxy example in quickstart documentation
Updated the proxy usage example to reflect the new Client initialization with a list of proxies.
* Correct bullet point formatting in quickstart.md
Fix formatting of bullet points in quickstart.md
* Update quickstart guide for wreq usage
More context added. And anchoring to API references for easy navigation between classes and models. To learn how to use it better
* Revise request examples in basic guide
Updated examples for GET and POST requests, including form data and headers. Improved clarity and consistency in code snippets.
* Change print statement to use response.status
---------
Co-authored-by: 0x676e67 <gngppz@gmail.com>
This page will help you get up and running with wreq in minutes.
3
+
This page covers the basics of making HTTP requests with wreq. By the end, you will be able to send requests, read responses, pass headers, work with JSON, and route traffic through a proxy.
4
4
5
5
---
6
6
7
-
## Basic GET Request
7
+
## Making a Request
8
+
9
+
wreq supports both async and blocking usage. The async client is the default and recommended approach for most use cases.
8
10
9
11
=== "Async"
10
12
```python
@@ -13,61 +15,88 @@ This page will help you get up and running with wreq in minutes.
wreq can emulate the TLS fingerprint and headers of real browsers, which is useful when connecting to servers that inspect these signals. Pass an [Emulation](../guide/emulation.md) preset to the `Client`:
0 commit comments