Probablemente no necesitarás usarlos directamente en tu código.

Pero en caso de que los necesites para un escenario avanzado, puedes agregar headers personalizados:

{* ../../docs_src/handling_errors/tutorial002_py310.py hl[14] *}

## Instalar manejadores de excepciones personalizados { #install-custom-exception-handlers }

### OpenAPI support { #openapi-support }

OpenAPI doesn't support a way to declare a *path parameter* to contain a *path* inside, as that could lead to scenarios that are difficult to test and define.

Nevertheless, you can still do it in **FastAPI**, using one of the internal tools from Starlette.

OkHttp is principled and avoids being overly configurable, especially when such configuration is
to workaround a buggy server, test invalid scenarios or that contradict the relevant RFC.
Other HTTP libraries exist that fill that gap allowing extensive customisation including potentially
invalid requests.

Example Limitations

* Does not allow GET with a body.

 * Due to the iterator's constructor calling advance() immediately, which requires
 * the adapt() method to be functional, we test the behavior using simple mock
 * scenarios that don't require complex filter setups.
 */
@ExtendWith(MockitoExtension.class)
class DirFileEntryAdapterIteratorTest {

    @Mock
    private SmbResource mockParent;

    @Mock

            assertArrayEquals(largeMic, parsed.getMechanismListMIC());
        }
    }

    @Nested
    @DisplayName("Parameterized Tests for Multiple Scenarios")
    class ParameterizedTests {

        @ParameterizedTest
        @MethodSource("provideMechanismCombinations")
        @DisplayName("Various mechanism combinations round-trip correctly")

En utilisant ces idées, les JWT peuvent servir à des scénarios bien plus sophistiqués.

Dans ces cas, plusieurs de ces entités peuvent avoir le même identifiant, disons `foo` (un utilisateur `foo`, une voiture `foo`, et un article de blog `foo`).

            // When & Then
            assertEquals(free, allocInfo.getFree());
        }

        @Test
        @DisplayName("Should handle overflow scenarios")
        void shouldHandleOverflowScenarios() {
            // Given - capacity at max, free space at max
            TestAllocInfo allocInfo = new TestAllocInfo(Long.MAX_VALUE, Long.MAX_VALUE);

            // When

        doNothing().when(response).reset();
        response.reset();
        verify(response).reset();
    }

    @Test
    @DisplayName("Test concrete implementation with multiple scenarios")
    void testConcreteImplementation() throws SMBProtocolDecodingException {
        // Create a concrete implementation for comprehensive testing

     *
     * - If the stack overflowed after set()/setValue() stored its result, then a call to
     * setException() will be a no-op because the Future is already done.
     *
     * Both scenarios are bad: The output Future might never complete, or, if it does complete, it
     * might not run some of its listeners. The likely result is that the app will hang. (And of

				}
				diskHealthCheckOK(ctx, err)
				if err != nil {
					// It is totally possible that xl.meta was overwritten
					// while being concurrently listed at the same time in
					// such scenarios the 'xl.meta' might get truncated
					if !IsErrIgnored(err, io.EOF, io.ErrUnexpectedEOF) {
						internalLogOnceIf(ctx, err, "metacache-walk-read-metadata")
					}
					continue
				}