```

Pode até ser um Stream infinito, em que você continua enviando dados.

## JSON Lines { #json-lines }

Nesses casos, é comum enviar "**JSON Lines**", um formato em que você envia um objeto JSON por linha.

Uma response teria um tipo de conteúdo `application/jsonl` (em vez de `application/json`) e o corpo seria algo como:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}

```

That line shows the URL where your app is being served on your local machine.

### Check it { #check-it }

Open your browser at [http://127.0.0.1:8000](http://127.0.0.1:8000).

You will see the JSON response as:

```JSON
{"message": "Hello World"}
```

### Interactive API docs { #interactive-api-docs }

Now go to [http://127.0.0.1:8000/docs](http://127.0.0.1:8000/docs).

If synchronous replication is configured above, replication is attempted right away prior to returning the PUT object response. In the event that the replication target is down, the `X-Amz-Replication-Status` is marked as `FAILED` and resynced with target when the scanner runs again.

`BackgroundTask`가 아닌 `BackgroundTasks`만 사용하면, 이를 *경로 처리 함수*의 매개변수로 사용할 수 있고 나머지는 **FastAPI**가 `Request` 객체를 직접 사용할 때처럼 대신 처리해 줍니다.

FastAPI에서 `BackgroundTask`만 단독으로 사용하는 것도 가능하지만, 코드에서 객체를 생성하고 이를 포함하는 Starlette `Response`를 반환해야 합니다.

더 자세한 내용은 [Starlette의 Background Tasks 공식 문서](https://www.starlette.dev/background/)에서 확인할 수 있습니다.

## 주의사항 { #caveat }

 *   <li>Excluding specific words from the results.</li>
 *   <li>Building the OpenSearch query and rescorer for the popular words search.</li>
 *   <li>Creating a {@link PopularWordsResponse} from the OpenSearch search response.</li>
 * </ul>
 *
 * @see Request
 * @see PopularWordsResponse
 */
public class PopularWordsRequest extends Request<PopularWordsResponse> {
    /**
     * Constructs a new popular words request.
     */

    $ unzip target/releases/fess-*.zip
    $ ./fess-*/bin/fess &

Wait for Fess to be ready (this may take up to 60 seconds):

    $ curl -s "http://localhost:8080/api/v1/health"

You should see a JSON response when Fess is ready.

#### 3. Clone Test Data

Required for SearchApiTests:

    $ git clone https://github.com/codelibs/fess-testdata.git /tmp/fess-testdata

#### 4. Run Integration Tests

                "summary": "Read Items",
                "operationId": "read_items_items__get",
                "responses": {
                    "200": {
                        "description": "Successful Response",
                        "content": {
                            "application/json": {
                                "schema": {}
                            }
                        }
                    }

        // Test RequestProcessor getResponse method
        CurlRequest.RequestProcessor processor = new CurlRequest.RequestProcessor("UTF-8", 2048);
        CurlResponse response = processor.getResponse();
        assertNotNull(response);
    }

    @Test
    public void testMultipleParamsWithSpecialCharacters() {
        CurlRequest request = new CurlRequest(Method.GET, "https://example.com");

<img src="/img/deployment/https/https05.drawio.svg">

### HTTP 回應 { #http-response }

應用會處理該請求，並將**純（未加密）的 HTTP 回應**送回 TLS 終止代理。

<img src="/img/deployment/https/https06.drawio.svg">

### HTTPS 回應 { #https-response }

TLS 終止代理接著會依照先前協商（起點是 `someapp.example.com` 的憑證）的方式**加密回應**，並傳回給瀏覽器。

接著，瀏覽器會驗證回應是否合法、是否使用正確的金鑰加密等。然後**解密回應**並處理。

    /**
     * Negotiate RDMA parameters
     *
     * @param request negotiation request parameters
     * @return negotiation response
     * @throws IOException if negotiation fails
     */
    public abstract RdmaNegotiateResponse negotiate(RdmaNegotiateRequest request) throws IOException;

    /**
     * Reset connection after recoverable error