those notices that do not pertain to any part of the Derivative Works, in at 
least one of the following places: within a NOTICE text file distributed as 
part of the Derivative Works; within the Source form or documentation, if 
provided along with the Derivative Works; or, within a display generated by 
the Derivative Works, if and wherever such third-party notices normally 

      new ImmutableMap.Builder<String, HashFunction>()
          .put("MD5", md5())
          .put("SHA", sha1()) // Not the official name, but still works
          .put("SHA1", sha1()) // Not the official name, but still works
          .put("sHa-1", sha1()) // Not the official name, but still works
          .put("SHA-1", sha1())
          .put("SHA-256", sha256())
          .put("SHA-384", sha384())
          .put("SHA-512", sha512())

## Pin your `fastapi` version { #pin-your-fastapi-version }

The first thing you should do is to "pin" the version of **FastAPI** you are using to the specific latest version that you know works correctly for your application.

For example, let's say you are using version `0.112.0` in your app.

/**
 * A class to represent the set of edges connecting an (implicit) origin node to a target node.
 *
 * <p>The {@link #nodeToOutEdge} map means this class only works on networks without parallel edges.
 * See {@link MultiEdgesConnecting} for a class that works with parallel edges.
 *
 * @author James Sexton
 * @param <E> Edge parameter type
 */
final class EdgesConnecting<E> extends AbstractSet<E> {

      new ImmutableMap.Builder<String, HashFunction>()
          .put("MD5", md5())
          .put("SHA", sha1()) // Not the official name, but still works
          .put("SHA1", sha1()) // Not the official name, but still works
          .put("sHa-1", sha1()) // Not the official name, but still works
          .put("SHA-1", sha1())
          .put("SHA-256", sha256())
          .put("SHA-384", sha384())
          .put("SHA-512", sha512())

        assertNotSame(client1, client2);
    }

    // Test constructor with different thread context
    @Test
    public void test_constructorInDifferentThread() throws Exception {
        // Test that constructor works in different thread
        final CrawlerEngineClient[] clientHolder = new CrawlerEngineClient[1];
        final Exception[] exceptionHolder = new Exception[1];

        Thread thread = new Thread(() -> {
            try {

Do you just want to **vibe**? 🎶

**FastAPI** now supports a new `@app.vibe()` decorator that embraces **modern AI coding best practices**. 🤖

## How It Works { #how-it-works }

The `@app.vibe()` decorator is intended to receive **any HTTP method** (`GET`, `POST`, `PUT`, `DELETE`, `PATCH`, etc.) and **any payload**.

You can read it as a header parameter and use it to resume the stream from where the client left off:

{* ../../docs_src/server_sent_events/tutorial004_py310.py hl[25,27,31] *}

## SSE with POST { #sse-with-post }

SSE works with **any HTTP method**, not just `GET`.

This is useful for protocols like [MCP](https://modelcontextprotocol.io) that stream SSE over `POST`:

{* ../../docs_src/server_sent_events/tutorial005_py310.py hl[14] *}

import okhttp3.HttpUrl;
import okhttp3.OkHttpClient;
import okhttp3.Request;
import okhttp3.logging.HttpLoggingInterceptor;
import okhttp3.logging.LoggingEventListener;

/**
 * Just checking compilation works
 */
public class OkHttpCaller {
  public static Call callOkHttp(HttpUrl url) {
    OkHttpClient client = new OkHttpClient
      .Builder()

You could put your XML content in a string, put that in a `Response`, and return it:

{* ../../docs_src/response_directly/tutorial002_py310.py hl[1,18] *}

## How a Response Model Works { #how-a-response-model-works }

When you declare a [Response Model - Return Type](../tutorial/response-model.md) in a path operation, **FastAPI** will use it to serialize the data to JSON, using Pydantic.