# Security { #security }

There are many ways to handle security, authentication and authorization.

And it normally is a complex and "difficult" topic.

In many frameworks and systems just handling security and authentication takes a big amount of effort and code (in many cases it can be 50% or more of all the code written).

import jakarta.servlet.http.HttpServletRequestWrapper;

/**
 * Wrapper for HTTP servlet requests in web API context.
 * This class extends HttpServletRequestWrapper to provide custom servlet path handling
 * for web API requests.
 */
public class WebApiRequest extends HttpServletRequestWrapper {
    /**
     * The custom servlet path for this web API request.
     */
    protected String servletPath;

    /**

   * a robolectric test.
   *
   * The functionality that will fail without a valid Context is primarily Cookies and URL Domain handling, but
   * may expand in the future.
   */
  fun initialize(applicationContext: Context) {
    if (PlatformRegistry.applicationContext == null) {
      // Make sure we aren't using an Activity or Service Context

        return this;
    }

    /**
     * Connects to the URL and executes the request.
     *
     * @param actionListener the action listener for handling the response
     * @param exceptionListener the exception listener for handling exceptions
     */
    public void connect(final Consumer<HttpURLConnection> actionListener, final Consumer<Exception> exceptionListener) {
        final Runnable task = () -> {

 */
package org.codelibs.fess.app.web.error;

import org.codelibs.fess.app.web.base.FessSearchAction;
import org.lastaflute.web.Execute;
import org.lastaflute.web.response.HtmlResponse;

/**
 * Action class for handling HTTP 404 Not Found error pages.
 * This action displays error pages when the requested resource
 * cannot be found on the server.
 */
public class ErrorNotfoundAction extends FessSearchAction {

    /**

        }

        @Override
        public String getName() {
            return name;
        }
    }

    /**
     * Transformer that throws exceptions for testing error handling
     */
    public static class ExceptionThrowingTransformer implements Transformer {
        private final String name;
        private boolean throwInTransform = false;
        private boolean throwInGetData = false;

import jcifs.CIFSContext;
import jcifs.http.NtlmHttpURLConnection;

/**
 * A <code>URLStreamHandler</code> used to provide NTLM authentication
 * capabilities to the default HTTPS handler. This acts as a wrapper,
 * handling authentication and passing control to the underlying
 * stream handler.
 *
 * @deprecated {@link NtlmHttpURLConnection} is broken by design.
 */
@Deprecated
public class Handler extends jcifs.http.Handler {

 *   <li><b>Model Version Handling</b>: When {@code preserve.model.version=true} is set, the consumer POM
 *       maintains the original model version (4.2.0) instead of downgrading to 4.0.0 for Maven 3 compatibility.
 *       This allows modern features like mixins to be preserved in the consumer POM.</li>
 * </ul>
 * <p>

import org.junit.jupiter.api.Test;

import jcifs.smb1.dcerpc.ndr.NdrBuffer;
import jcifs.smb1.dcerpc.ndr.NdrException;

/**
 * Unit tests for {@link DcerpcMessage}. The tests exercise flag handling,
 * result extraction, header encoding/decoding, and the round-trip of an
 * encode/decode operation.
 */
public class DcerpcMessageTest {

    /**

    This is for client errors, invalid authentication, invalid data, etc. Not for server
    errors in your code.

    Read more about it in the
    [FastAPI docs for Handling Errors](https://fastapi.tiangolo.com/tutorial/handling-errors/).

    ## Example

    ```python
    from fastapi import FastAPI, HTTPException

    app = FastAPI()

    items = {"foo": "The Foo Wrestlers"}