/**
 * [DNS over HTTPS implementation][doh_spec].
 *
 * > A DNS API client encodes a single DNS query into an HTTP request
 * > using either the HTTP GET or POST method and the other requirements
 * > of this section.  The DNS API server defines the URI used by the
 * > request through the use of a URI Template.
 *
 * [doh_spec]: https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-13
 */
class DnsOverHttps internal constructor(

/// info | Примечание

В веб-сокете вызывать `HTTPException` не имеет смысла. Вместо этого нужно использовать `WebSocketException`.

Закрывающий статус код можно использовать из <a href="https://tools.ietf.org/html/rfc6455#section-7.4.1" class="external-link" target="_blank">valid codes defined in the specification</a>.

///

### Веб-сокеты с зависимостями: проверка в действии { #try-the-websockets-with-dependencies }

  count: 50
  avatarUrl: https://avatars.githubusercontent.com/in/68672?v=4
  url: https://github.com/apps/pre-commit-ci
github-actions:
  login: github-actions
  count: 26
  avatarUrl: https://avatars.githubusercontent.com/in/15368?v=4
  url: https://github.com/apps/github-actions
Kludex:
  login: Kludex
  count: 25
  avatarUrl: https://avatars.githubusercontent.com/u/7353520?u=df8a3f06ba8f55ae1967a3e2d5ed882903a4e330&v=4

* The frontend stores that token temporarily somewhere.
* The user clicks in the frontend to go to another section of the frontend web app.
* The frontend needs to fetch some more data from the API.
    * But it needs authentication for that specific endpoint.

<plugins>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>

### Custom OpenAPI content type { #custom-openapi-content-type }

Using this same trick, you could use a Pydantic model to define the JSON Schema that is then included in the custom OpenAPI schema section for the *path operation*.

And you could do this even if the data type in the request is not JSON.

     */
    int getConnTimeout();

    /**
     * Property {@code jcifs.smb.client.sessionTimeout} (int, default 35000)
     *
     *
     * @return timeout for SMB sessions, in milliseconds
     */
    int getSessionTimeout();

    /**
     *
     * Property {@code jcifs.smb.client.responseTimeout} (int, default 30000)
     *

    private static final Logger logger = LogManager.getLogger(FessActionAdjustmentProvider.class);

    // _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
    // you can adjust your actions by overriding
    // default methods defined at the interface
    // _/_/_/_/_/_/_/_/_/_/

    protected Map<String, List<Pair<String, String>>> responseHeaderMap = new HashMap<>();

### Type de contenu OpenAPI personnalisé

En utilisant cette même astuce, vous pouvez utiliser un modèle Pydantic pour définir le schéma JSON qui est ensuite inclus dans la section de schéma OpenAPI personnalisée pour le *chemin* concerné.

Et vous pouvez le faire même si le type de données dans la requête n'est pas au format JSON.

        });
        return asJson(new ApiResponse().status(Status.OK).result());
    }

    /**
     * Deletes all old crawling info sessions except currently running ones.
     *
     * @return JSON response indicating the deletion status
     */
    // DELETE /api/admin/crawlinginfo/all
    @Execute
    public JsonResponse<ApiResult> delete$all() {