* - 2 requests happen concurrently to a host that can be coalesced onto a single connection.
   * - Both request discover no existing connection. They both make a connection.
   * - The first request "wins the race".
   * - The second request discovers it "lost the race" and closes the connection it just opened.
   * - The second request uses the coalesced connection from request1.

# Request Files { #request-files }

You can define files to be uploaded by the client using `File`.

/// info

To receive uploaded files, first install [`python-multipart`](https://github.com/Kludex/python-multipart).

Make sure you create a [virtual environment](../virtual-environments.md), activate it, and then install it, for example:

```console
$ pip install python-multipart
```

This is because uploaded files are sent as "form data".

Some use cases include:

* Converting non-JSON request bodies to JSON (e.g. [`msgpack`](https://msgpack.org/index.html)).
* Decompressing gzip-compressed request bodies.
* Automatically logging all request bodies.

## Handling custom request body encodings { #handling-custom-request-body-encodings }

Let's see how to make use of a custom `Request` subclass to decompress gzip requests.

---
- job:
    name: "elastic+elasticsearch+pull-request+part-2-fips"
    display-name: "elastic / elasticsearch - pull request part-2 fips"
    description: "Testing of Elasticsearch pull requests - part-2 fips"
    workspace: "/dev/shm/elastic+elasticsearch+pull-request+part-2-fips"
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:
            - "${ghprbActualCommit}"

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-upgrade-tests"
    display-name: "elastic / elasticsearch - pull request packaging-upgrade-tests"
    description: "Testing of Elasticsearch pull requests - packaging-upgrade-tests"
    project-type: matrix
    node: master
    child-workspace: "/dev/shm/elastic+elasticsearch+pull-request+packaging-upgrade-tests"
    scm:
      - git:

## Pull Request 리뷰하기 { #review-pull-requests }

다른 사람들이 만든 pull request를 리뷰하는 데 저를 도와줄 수 있습니다.

다시 한번 말하지만, 최대한 친절하게 리뷰해 주세요. 🤗

---

Pull request를 리뷰할 때 고려해야 할 사항과 방법은 다음과 같습니다:

### 문제 이해하기 { #understand-the-problem }

* 먼저, 해당 pull request가 해결하려는 **문제를 이해하는지** 확인하세요. GitHub Discussion 또는 이슈에서 더 긴 논의가 있었을 수도 있습니다.

from starlette.requests import HTTPConnection as HTTPConnection  # noqa: F401

# `Request` class

You can declare a parameter in a *path operation function* or dependency to be of type `Request` and then you can access the raw request object directly, without any validation, etc.

Read more about it in the [FastAPI docs about using Request directly](https://fastapi.tiangolo.com/advanced/using-request-directly/)

You can import it directly from `fastapi`:

```python
from fastapi import Request
```

/// tip

 */
public abstract class Request<T extends Response> {
    /**
     * Constructs a new request.
     */
    public Request() {
        // nothing
    }

    /**
     * Executes the request.
     * @param client The OpenSearch client.
     * @return A Promise that will be resolved with the response or rejected with an error.
     */
    public Deferred<T>.Promise execute(final Client client) {

# Arquivos de Requisição { #request-files }

Você pode definir arquivos para serem enviados pelo cliente usando `File`.

/// info | Informação

Para receber arquivos enviados, primeiro instale [`python-multipart`](https://github.com/Kludex/python-multipart).

Garanta que você criou um [ambiente virtual](../virtual-environments.md), o ativou e então o instalou, por exemplo:

```console
$ pip install python-multipart
```