# HTTP Basic Auth { #http-basic-auth }

For the simplest cases, you can use HTTP Basic Auth.

In HTTP Basic Auth, the application expects a header that contains a username and a password.

If it doesn't receive it, it returns an HTTP 401 "Unauthorized" error.

And returns a header `WWW-Authenticate` with a value of `Basic`, and an optional `realm` parameter.

That tells the browser to show the integrated prompt for a username and password.

    * So, by using FastAPI you are saving development time, bugs, lines of code, and you would probably get the same performance (or better) you would...

The same way, you could raise an `HTTPException` or similar in the exit code, after the `yield`.

/// tip

This is a somewhat advanced technique, and in most of the cases you won't really need it, as you can raise exceptions (including `HTTPException`) from inside of the rest of your application code, for example, in the *path operation function*.

But it's there for you if you need it. 🤓

///

        assertEquals(8, serverData.encryptionKey.length);
        assertEquals(16, serverData.guid.length);
    }

    /**
     * Test edge cases for numeric fields
     */
    @Test
    @DisplayName("Test edge cases for numeric fields")
    public void testNumericFieldsEdgeCases() {
        // Test maximum values for int fields
        serverData.sflags2 = Integer.MAX_VALUE;

     * {@link Parser#parseInvocation(ParserRequest)} this method will return {@code true} and invoker should
     * handle this request as "early failure". In these cases, {@link #options()} usually is absent.
     */
    boolean parsingFailed();

    /**
     * Returns {@code true} if this call happens in "embedded" mode.
     *
     * @see ParserRequest#embedded()
     */

            // Then
            assertEquals(443, httpsPort);
            assertEquals(80, httpPort);
            assertNotEquals(httpsPort, httpPort);
        }
    }

    @Nested
    @DisplayName("Edge Cases")
    class EdgeCaseTests {

        @Test
        @DisplayName("Should handle reflection access to protected method")
        void testProtectedMethodAccess() throws Exception {
            // Given

# Extending OpenAPI { #extending-openapi }

There are some cases where you might need to modify the generated OpenAPI schema.

In this section you will see how.

## The normal process { #the-normal-process }

The normal (default) process, is as follows.

A `FastAPI` application (instance) has an `.openapi()` method that is expected to return the OpenAPI schema.

     */
    private static Stream<Arguments> provideErrorClassAndCodeForGetErrorString() {
        return Stream.of(
                // SUCCESS
                Arguments.of(NbtException.SUCCESS, 0, "SUCCESS"),

                // ERR_NAM_SRVC
                // Note: FMT_ERR case has a bug in NbtException.getErrorString() - missing break statement causes fallthrough

is resilient and can automatically recover from some connectivity failures. In this case, the `connectFailed()` event is not terminal and not followed by `callFailed()`. Event listeners will receive multiple events of the same type when retries are attempted.

A single HTTP call may require follow-up requests to be made to handle authentication challenges, redirects, and HTTP-layer timeouts. In such cases multiple connections, requests, and responses may be attempted. Follow-ups are another...

        switch (request.getUrl().encodedPath()) {
          case "/v1/login/auth/":
              return new MockResponse.Builder()
                  .code(200)
                  .build();
          case "/v1/check/version/":
              return new MockResponse.Builder()
                  .code(200)
                  .body("version=9")
                  .build();
          case "/v1/profile/info":