* This class provides a simple way to construct RequestData objects with method chaining.
 *
 * <p>Usage example:</p>
 * <pre>
 * RequestData request = RequestDataBuilder.newRequestData()
 *     .method("GET")
 *     .url("https://example.com")
 *     .weight(1.0f)
 *     .build();
 * </pre>
 *
 * <p>The builder is implemented using an inner class {@link RequestDataContext} that handles

> Requests est l'un des packages Python les plus téléchargés de tous les temps

La façon dont vous l'utilisez est très simple. Par exemple, pour faire une requête `GET`, vous devez écrire :

```Python
response = requests.get("http://example.com/some/url")
```

En contrepartie l'API _des opérations de chemin_ de FastAPI pourrait ressembler à ceci :

```Python hl_lines="1"
@app.get("/some/url")

It would also mean that if you get data from the `Request` object directly (for example, read the body) it won't be validated, converted or documented (with OpenAPI, for the automatic API user interface) by FastAPI.

Although any other parameter declared normally (for example, the body with a Pydantic model) would still be validated, converted, annotated, etc.

If you want to secure your API, there are several better things you can do, for example:

* Make sure you have well defined Pydantic models for your request bodies and responses.
* Configure any required permissions and roles using dependencies.
* Never store plaintext passwords, only password hashes.

# v1.10.8

[Documentation](https://docs.k8s.io) & [Examples](https://releases.k8s.io/release-1.10/examples)

## Downloads for v1.10.8


filename | sha256 hash
-------- | -----------

        "full_name": "John Doe",
        "email": "johndoe@example.com",
        "hashed_password": "$argon2id$v=19$m=65536,t=3,p=4$wagCPXjifgvUFBzq4hqe3w$CYaIb8sB+wtD+Vu/P4uod1+Qof8h+1g7bbDlBID48Rc",
        "disabled": False,
    },
    "alice": {
        "username": "alice",
        "full_name": "Alice Chains",
        "email": "alicechains@example.com",

 * flags is necessary to distinguish which type of Named Pipe behavior
 * is desired.
 *
 * <table border="1">
 * <caption>SmbNamedPipe Constructor Examples</caption>
 * <tr>
 * <td colspan="2"><b><code>SmbNamedPipe</code> Constructor Examples</b></td>
 * <tr><td ><b>Code Sample</b></td><td><b>Description</b></td></tr>
 * <tr><td ><pre>
 * new SmbNamedPipe( "smb1://server/IPC$/PIPE/foo",

    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>org.example</groupId>
        <artifactId>parent</artifactId>
        <version>0.0.1-SNAPSHOT</version>
        <relativePath>./parent-pom.xml</relativePath>
    </parent>

    <artifactId>child</artifactId>

---

But for this example, we'll use a very simple HTML document with some JavaScript, all inside a long string.

This, of course, is not optimal and you wouldn't use it for production.

In production you would have one of the options above.

But it's the simplest way to focus on the server-side of WebSockets and have a working example:

 * </p>
 *
 * <p>
 * Example usage:
 * </p>
 *
 * <pre>
 * {@code
 * try (InputStream in = new FileInputStream("example.pdf")) {
 *     ExtractData extractData = new ExtractorBuilder(crawlerContainer, in, new HashMap<>())
 *         .mimeType("application/pdf")
 *         .filename("example.pdf")
 *         .maxContentLength(1024 * 1024)
 *         .extract();
 *