import jcifs.Configuration;
import jcifs.RuntimeCIFSException;
import jcifs.internal.dtyp.SecurityDescriptor;
import jcifs.internal.util.SMBUtil;

/**
 * Response for SMB1 NT Transaction security descriptor query.
 *
 * This response contains the Windows security descriptor retrieved
 * from the server, including access control information.
 */

    repeat(2) {
      val response = client.newCall(request).execute()

      if (response.code == 401) {
        assertThat(response.body.string()).isEqualTo("{\"error\":{\"message\":\"No auth credentials found\",\"code\":401}}")
        request = request.newBuilder().header("Authorization", "XYZ").build()
      } else {
        response.processEventSource(listener)
        listener.assertOpen()

import org.codelibs.fess.util.RenderDataUtil;
import org.dbflute.optional.OptionalEntity;
import org.dbflute.optional.OptionalThing;
import org.lastaflute.web.Execute;
import org.lastaflute.web.response.HtmlResponse;
import org.lastaflute.web.response.render.RenderData;
import org.lastaflute.web.ruts.process.ActionRuntime;

import jakarta.annotation.Resource;

/**
 * Admin action for File Authentication management.
 *
 */

            try {
                response.setEncoding(encoding);
                response.setHttpStatusCode(con.getResponseCode());
                response.setHeaders(con.getHeaderFields());
            } catch (final Exception e) {
                throw new CurlException("Failed to access the response.", e);
            }
            writeContent(() -> {
                try {

   *
   * ### Duplex Transmission
   *
   * With regular HTTP calls the request always completes sending before the response may begin
   * receiving. With duplex the request and response may be interleaved! That is, request body bytes
   * may be sent after response headers or body bytes have been received.
   *
   * Though any call may be initiated as a duplex call, only web servers that are specially

            }
        }
        return null;
    }

    /**
     * Gets the appropriate response for the specified SSO response type.
     *
     * @param responseType The type of SSO response required (e.g., METADATA, LOGOUT)
     * @return The action response from the SSO authenticator, or null if SSO is not available
     */
    public ActionResponse getResponse(final SsoResponseType responseType) {

import org.codelibs.fess.app.web.api.admin.FessApiAdminAction;
import org.codelibs.fess.helper.ProcessHelper;
import org.codelibs.fess.opensearch.config.exentity.FailureUrl;
import org.lastaflute.web.Execute;
import org.lastaflute.web.response.JsonResponse;

import jakarta.annotation.Resource;

/**
 * API action for admin failure URL.
 *
 */
public class ApiAdminFailureurlAction extends FessApiAdminAction {

    }

    @Test
    @DisplayName("initResponse prepares a response instance")
    void initResponseCreatesResponse() {
        SmbComNTCreateAndX req = createRequest(0, 0);
        when(mockContext.getConfig()).thenReturn(mockConfig);
        SmbComNTCreateAndXResponse resp = req.initResponse(mockContext);
        assertNotNull(resp, "Response should not be null after init");

# Hintergrundtasks

Sie können Hintergrundtasks (Hintergrund-Aufgaben) definieren, die *nach* der Rückgabe einer Response ausgeführt werden sollen.

Das ist nützlich für Vorgänge, die nach einem Request ausgeführt werden müssen, bei denen der Client jedoch nicht unbedingt auf den Abschluss des Vorgangs warten muss, bevor er die Response erhält.

Hierzu zählen beispielsweise:

* E-Mail-Benachrichtigungen, die nach dem Ausführen einer Aktion gesendet werden:

# Background Tasks { #background-tasks }

You can define background tasks to be run *after* returning a response.

This is useful for operations that need to happen after a request, but that the client doesn't really have to be waiting for the operation to complete before receiving the response.

This includes, for example:

* Email notifications sent after performing an action: