* else a dependency collection request will be done.
     *
     * @return the id of the path scope
     */
    String pathScope() default "";

    /**
     * The request type, in case the default one is not correct.
     * Valid values are {@code collect}, {@code flatten}, or {@code resolve}.
     *
     * @return the request type
     */
    String requestType() default "";

    // Test constructor
    @Test
    public void test_constructor_withValidParameters() {
        // Test normal construction
        assertNotNull(securityResourceProvider);

        // Verify fields are set correctly
        InvertibleCryptographer providedInvertible = securityResourceProvider.providePrimaryInvertibleCryptographer();
        OneWayCryptographer providedOneWay = securityResourceProvider.providePrimaryOneWayCryptographer();

import com.google.common.annotations.GwtCompatible;
import com.google.common.annotations.GwtIncompatible;
import com.google.common.annotations.J2ktIncompatible;

/**
 * Simple derived class to verify that we handle generics correctly.
 *
 * @author Kevin Bourrillion
 */
@GwtCompatible
public class DerivedComparable extends BaseComparable {
  public DerivedComparable(String s) {
    super(s);
  }

# Properties used to build to the DEB package
#

# Environment file
packaging.env.file=/etc/default/fess

# Simple marker to check that properties are correctly overridden
packaging.type=deb

# Custom header for package scripts
packaging.scripts.header=#!/bin/sh${line.separator}set -e

        if (project.getPath().equals(":libs:elasticsearch-core") == false) {
            // ideally we would configure this as a default dependency. But Default dependencies do not work correctly
            // with gradle project dependencies as they're resolved to late in the build and don't setup according task
            // dependencies properly

La manera en que los formularios HTML (`<form></form>`) envían los datos al servidor normalmente usa una codificación "especial" para esos datos, es diferente de JSON.

**FastAPI** se encargará de leer esos datos del lugar correcto en lugar de JSON.

/// note | Detalles técnicos

Los datos de formularios normalmente se codifican usando el "media type" `application/x-www-form-urlencoded`.

Verás la documentación automática de la API para la sub-aplicación, incluyendo solo sus propias _path operations_, todas bajo el prefijo correcto del sub-path `/subapi`:

<img src="/img/tutorial/sub-applications/image02.png">

## Wildcards { #wildcards }

It's also possible to declare the list as `"*"` (a "wildcard") to say that all are allowed.

But that will only allow certain types of communication, excluding everything that involves credentials: Cookies, Authorization headers like those used with Bearer Tokens, etc.

So, for everything to work correctly, it's better to specify explicitly the allowed origins.

    /** The specified user already exists */
    int NT_STATUS_USER_EXISTS = 0xC0000063;
    /** The specified user does not exist */
    int NT_STATUS_NO_SUCH_USER = 0xC0000064;
    /** The specified network password is not correct */
    int NT_STATUS_WRONG_PASSWORD = 0xC000006a;
    /** Logon failure: unknown user name or bad password */
    int NT_STATUS_LOGON_FAILURE = 0xC000006d;
    /** Logon failure: user account restriction */

Vous verrez la documentation API automatique pour la sous‑application, n'incluant que ses propres _chemins d'accès_, tous sous le préfixe de sous‑chemin correct `/subapi` :

<img src="/img/tutorial/sub-applications/image02.png">