Esto también significa que si estás dentro de una función de utilidad que estás llamando dentro de tu *path operation function*, y lanzas el `HTTPException` desde dentro de esa función de utilidad, no se ejecutará el resto del código en la *path operation function*, terminará ese request de inmediato y enviará el error HTTP del `HTTPException` al cliente.

///

Este parámetro no crea ese endpoint / *path operation*, pero declara que la URL `/token` será la que el cliente deberá usar para obtener el token. Esa información se usa en OpenAPI, y luego en los sistemas de documentación interactiva del API.

Pronto también crearemos la verdadera *path operation*.

/// info | Información

import okhttp3.internal.publicsuffix.ResourcePublicSuffixList.Companion.PUBLIC_SUFFIX_RESOURCE
import okio.BufferedSink
import okio.ByteString
import okio.ByteString.Companion.encodeUtf8
import okio.FileSystem
import okio.Path
import okio.Path.Companion.toPath
import okio.buffer

/**
 * Downloads the public suffix list from https://publicsuffix.org/list/public_suffix_list.dat and
 * transforms the file into an efficient format used by OkHttp.
 *
 *

        return dstIndex - start;
    }

    @Override
    int writeBytesWireFormat(final byte[] dst, final int dstIndex) {
        int n = writeString(path, dst, dstIndex);
        writeInt2(useUnicode ? path.length() * 2 : n, dst, namelen_index);
        return n;
    }

    @Override
    int readParameterWordsWireFormat(final byte[] buffer, final int bufferIndex) {
        return 0;

            String version,
            String type,
            String classifier,
            List<ArtifactRepository> remoteRepositories,
            List<String> path,
            Throwable t) {
        super(message, groupId, artifactId, version, type, classifier, remoteRepositories, path, t);
    }

    public ArtifactResolutionException(
            String message,
            String groupId,
            String artifactId,

     *
     * @param path file path
     * @param operation operation performed
     * @param success whether operation succeeded
     * @param username user performing operation
     */
    public void logFileAccess(String path, String operation, boolean success, String username) {
        Map<String, Object> context = getContextMap();
        context.put("path", sanitizePath(path));

    void fixupDomain(String domain);

    /**
     * Reduces path consumed by the given value
     *
     * @param i the number of characters to strip from path consumed
     */
    void stripPathConsumed(int i);

    @Override
    DfsReferralDataInternal next();

    /**
     * Set the UNC path link for this referral
     *
     * @param link the UNC path link to set
     */
    void setLink(String link);

    /**

 */
public class Trans2GetDfsReferral extends SmbComTransaction {

    private final int maxReferralLevel;

    private final DfsReferralRequestBuffer request;

    /**
     * Constructs a Trans2GetDfsReferral request with default referral level.
     *
     * @param config the configuration to use
     * @param filename the DFS path to get referrals for
     */

# 본문 - 다중 매개변수

지금부터 `Path`와 `Query`를 어떻게 사용하는지 확인하겠습니다.

요청 본문 선언에 대한 심화 사용법을 알아보겠습니다.

## `Path`, `Query` 및 본문 매개변수 혼합

당연하게 `Path`, `Query` 및 요청 본문 매개변수 선언을 자유롭게 혼합해서 사용할 수 있고, **FastAPI**는 어떤 동작을 할지 압니다.

또한, 기본 값을 `None`으로 설정해 본문 매개변수를 선택사항으로 선언할 수 있습니다.

{* ../../docs_src/body_multiple_params/tutorial001.py hl[19:21] *}

/// note | 참고

이 경우에는 본문으로 부터 가져온 `	item`은 기본값이 `None`이기 때문에, 선택사항이라는 점을 유의해야 합니다.

///

        when(session.getAttribute("npa-workgroup")).thenReturn(auth);

        // Test various path formats
        String[] testPaths = { "/", "/workgroup/", "/workgroup/server/", "/workgroup/server/share/", "/workgroup/server/share/file.txt" };

        for (String path : testPaths) {
            when(request.getPathInfo()).thenReturn(path);

            assertDoesNotThrow(() -> networkExplorer.doGet(request, response));