import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Logoff request message. This command is used to terminate an SMB2 session.
 *
 * @author mbechler
 *
 */
public class Smb2LogoffRequest extends ServerMessageBlock2Request<Smb2LogoffResponse> {

    /**
     * Constructs an SMB2 logoff request with the given configuration.
     *
     * @param config the configuration for this request
     */

    OkHttpClient client = new OkHttpClient();

    // Create request for remote resource.
    Request request = new Request.Builder()
        .url(ENDPOINT)
        .build();

    // Execute the request and retrieve the response.
    try (Response response = client.newCall(request).execute()) {
      // Deserialize HTTP response to concrete type.
      ResponseBody body = response.body();

     *
     * @param request The version request, must not be {@code null}.
     * @return The version result, never {@code null}.
     * @throws VersionResolverException If the metaversion could not be resolved.
     */
    @Nonnull
    VersionResolverResult resolve(@Nonnull VersionResolverRequest request) throws VersionResolverException;

                }))
                .status(Status.OK)
                .result());
    }

    /**
     * Creates a new boost document rule setting.
     *
     * @param body the request body containing boost document rule information
     * @return JSON response with result status
     */
    // POST /api/admin/boostdoc/setting
    @Execute

- Temporary credentials do not need to be stored with the application but are generated dynamically and provided to the application when requested. When (or even before) the temporary credentials expire, the application can request new credentials.

Following are advantages for using temporary credentials:

    @Test
    @DisplayName("Test prepare method with valid request")
    void testPrepareWithValidRequest() {
        // Given
        doNothing().when(response).prepare(request);

        // When
        response.prepare(request);

        // Then
        verify(response).prepare(request);
    }

    @Test
    @DisplayName("Test prepare method with null request")
    void testPrepareWithNullRequest() {

     * @param basedir The base directory to resolve relative paths against, may be {@code null}.
     * @param request The model building request that holds further settings, must not be {@code null}.
     */
    void alignToBaseDirectory(Model model, File basedir, ModelBuildingRequest request);

        int combinedFlags = 0x0003; // Multiple flags set
        request.setCloseFlags(combinedFlags);

        byte[] buffer = new byte[256];
        int written = request.writeBytesWireFormat(buffer, 0);

        assertEquals(24, written);
        assertEquals(combinedFlags, SMBUtil.readInt2(buffer, 2));
    }

    @Test
    @DisplayName("Test request state after multiple operations")

You could create an API with a *path operation* that could trigger a request to an *external API* created by someone else (probably the same developer that would be *using* your API).

The process that happens when your API app calls the *external API* is named a "callback". Because the software that the external developer wrote sends a request to your API and then your API *calls back*, sending a request to an *external API* (that was probably created by the same developer).

        }
    }

    /**
     * Gets the appropriate web API manager for the given request.
     *
     * @param request The HTTP servlet request
     * @return The matching web API manager, or null if no match found
     */
    public WebApiManager get(final HttpServletRequest request) {
        final String servletPath = request.getServletPath();
        if (logger.isDebugEnabled()) {