{
			name:     "1",
			metadata: map[string]string{"content-type": "application/octet-stream", "etag": "de75a98baf2c6aef435b57dd0fc33c86", "x-amz-storage-class": "STANDARD"},
			want:     map[string]string{"content-type": "application/octet-stream", "etag": "de75a98baf2c6aef435b57dd0fc33c86"},
		},
		{
			name:     "2",

### What is "Mounting" { #what-is-mounting }

"Mounting" means adding a complete "independent" application in a specific path, that then takes care of handling all the sub-paths.

This is different from using an `APIRouter` as a mounted application is completely independent. The OpenAPI and docs from your main application won't include anything from the mounted application, etc.

     * @param contextPath the context path for the web application
     */
    public FessBoot(final int port, final String contextPath) {
        super(port, contextPath);
    }

    /**
     * Prepares and returns the web application path.
     * Checks for the fess.webapp.path system property first, then falls back to the parent implementation.
     *
     * @return the web application path
     */
    @Override

        // Add a sequence instead of APPLICATION tagged object
        DERSequence wrongTag = new DERSequence(new ASN1Encodable[] { new ASN1Integer(5) });
        innerContent.write(wrongTag.getEncoded());

        byte[] content = innerContent.toByteArray();

        // Create GSS-API wrapper
        ByteArrayOutputStream baos = new ByteArrayOutputStream();
        baos.write(0x60); // APPLICATION 0
        baos.write(content.length);

    }

    /**
     * Returns the application type identifier for this Fess application.
     *
     * @return the application type string "FES"
     */
    @Override
    protected String myAppType() { // for framework
        return APP_TYPE;
    }

    /**
     * Returns the user type identifier for this application.
     *

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Waiting for application startup.
     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Waiting for application startup.
     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Waiting for application startup.

    }

    public void test_add_overwrite() {
        fileTypeHelper.add("application/pdf", "pdf");
        assertEquals("pdf", fileTypeHelper.get("application/pdf"));

        fileTypeHelper.add("application/pdf", "document");
        assertEquals("document", fileTypeHelper.get("application/pdf"));
    }

    public void test_add_withNullMimetype() {
        fileTypeHelper.add(null, "test");

# Lifespan Events { #lifespan-events }

You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**.

The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.

For some types of applications you might want to add dependencies to the whole application.

Similar to the way you can [add `dependencies` to the *path operation decorators*](dependencies-in-path-operation-decorators.md){.internal-link target=_blank}, you can add them to the `FastAPI` application.

In that case, they will be applied to all the *path operations* in the application:

{* ../../docs_src/dependencies/tutorial012_an_py39.py hl[16] *}

<font color="#4E9A06">INFO</font>:     Waiting for application startup.
<font color="#4E9A06">INFO</font>:     Application startup complete.
<font color="#4E9A06">INFO</font>:     Started server process [<font color="#06989A">27369</font>]
<font color="#4E9A06">INFO</font>:     Waiting for application startup.
<font color="#4E9A06">INFO</font>:     Application startup complete.