getMockRequest().addHeader("user-agent",
                "Mozilla/5.0 (iPhone; CPU iPhone OS 14_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.1 Mobile/15E148 Safari/604.1");
        assertEquals(UserAgentType.SAFARI, userAgentHelper.getUserAgentType());
    }

    @Test
    public void test_getUserAgentType_operaModern() {

Example:

Source (English):

```
## Another module with `APIRouter` { #another-module-with-apirouter }
```

Translate with (German):

```
## Ein weiteres Modul mit `APIRouter` { #another-module-with-apirouter }
```

Do NOT translate with (German) – notice the added period:

```
## Ein weiteres Modul mit `APIRouter`. { #another-module-with-apirouter }
```

- machine learning: машинне навчання
- dependency injection: впровадження залежностей
- digest (HTTP): дайджест
- basic authentication (HTTP): базова автентифікація
- JSON schema: Схема JSON
- password flow: потік паролю
- mobile: мобільний
- body: тіло
- form: форма
- path: шлях
- query: запит
- cookie: кукі
- header: заголовок
- startup: запуск
- shutdown: вимкнення
- lifespan: тривалість життя
- authorization: авторизація

        ":with_tpu_support_flag",
    ],
    visibility = ["//visibility:public"],
)

# Specifies via a config setting if this is a mobile build or not, makes
# it easier to combine settings later.
selects.config_setting_group(
    name = "mobile",
    match_any = [
        ":android",
        ":chromiumos",
        # TODO(jakeharmon8): Move all platform configs to TSL with fuchsia (non-blocking)

* the database session
* the disk
* the domain
* the engine
* the fake X
* the HTTP GET method
* the item
* the library
* the lifespan
* the lock
* the middleware
* the mobile application
* the module
* the mounting
* the network
* the origin
* the override
* the payload
* the processor
* the property
* the proxy
* the pull request
* the query
* the RAM

And to communicate using WebSockets with your backend you would probably use your frontend's utilities.

Or you might have a native mobile application that communicates with your WebSocket backend directly, in native code.

Or you might have any other way to communicate with the WebSocket endpoint.

---

# Security - First Steps { #security-first-steps }

Let's imagine that you have your **backend** API in some domain.

And you have a **frontend** in another domain or in a different path of the same domain (or in a mobile application).

And you want to have a way for the frontend to authenticate with the backend, using a **username** and **password**.

We can use **OAuth2** to build that with **FastAPI**.

  /**
   * The HTTP <a href="https://wicg.github.io/ua-client-hints/#sec-ch-ua-mobile">{@code
   * Sec-CH-UA-Mobile}</a> header field name.
   *
   * @since 30.0
   */
  public static final String SEC_CH_UA_MOBILE = "Sec-CH-UA-Mobile";

  /**
   * The HTTP <a href="https://wicg.github.io/ua-client-hints/#sec-ch-ua-wow64">{@code

labels.postOfficeBox=Post Office Box
labels.user_initials=Initials
labels.initials=Initials
labels.user_carLicense=Car License
labels.carLicense=Car License
labels.user_mobile=Mobile
labels.mobile=Mobile
labels.user_postalAddress=Postal Address
labels.postalAddress=Postal Address
labels.user_city=City
labels.city=City
labels.user_teletexTerminalIdentifier=Teletex Terminal Identifier

        @Override
        public String getLdapAttrPostalAddress() {
            return "postalAddress";
        }

        @Override
        public String getLdapAttrMobile() {
            return "mobile";
        }

        @Override
        public String getLdapAttrCarLicense() {
            return "carLicense";
        }

        @Override
        public String getLdapAttrInitials() {