# Custom Response Classes - File, HTML, Redirect, Streaming, etc.

There are several custom response classes you can use to create an instance and return them directly from your *path operations*.

Read more about it in the [FastAPI docs for Custom Response - HTML, Stream, File, others](https://fastapi.tiangolo.com/advanced/custom-response/).

You can import them directly from `fastapi.responses`:

```python
from fastapi.responses import (
    FileResponse,

        }

    fun getDependencies() = classes.map { it.value.outputClassFilename to it.value.dependencies.map { it.outputClassFilename } }.toMap()
}


class ClassDetails(val outputClassName: String) {
    var visited: Boolean = false
    val dependencies: MutableSet<ClassDetails> = linkedSetOf()
    val outputClassFilename
        get() = "$outputClassName.class"
}


class PackagePatterns(givenPrefixes: Set<String>) {

import org.jspecify.annotations.NullUnmarked;

/** Basic sanity tests for classes in {@code common.base}. */

@GwtIncompatible
@NullUnmarked
public class PackageSanityTests extends AbstractPackageSanityTests {
  public PackageSanityTests() {
    // package private classes like FunctionalEquivalence are tested through the public API.
    publicApiOnly();
  }

You can import it directly form `fastapi`:

```python
from fastapi import WebSocketDisconnect
```

::: fastapi.WebSocketDisconnect

## WebSockets - additional classes

Additional classes for handling WebSockets.

Provided directly by Starlette, but you can import it from `fastapi`:

```python
from fastapi.websockets import WebSocketDisconnect, WebSocketState
```

            <phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <instructions>
            <!-- Silence a warning that claims that META-INF/versions/9/... is the "wrong directory" for our classes. -->
            <_fixupmessages>^Classes found in the wrong directory: .*</_fixupmessages>

~~ under the License.

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2016-05-29
 -----

Maven Compat

 Maven2 classes maintained as compatibility layer for plugins that need to keep Maven2 compatibility.

 Plugins should avoid these classes and be updated to use only Maven3 dependencies (and require Maven3): see

        assertEquals(str, result);
    }

    /**
     * Test that default filter allows org.codelibs classes
     *
     * @throws Exception
     */
    public void testFromBinaryToObject_DefaultFilter_AllowsCodelibsClasses() throws Exception {
        // The default filter should allow org.codelibs.* classes
        final TestSerializableClass obj = new TestSerializableClass("test", 456);

     */
    private String artifactId;

    /**
     * The version of the extension.
     */
    private String version;

    /**
     * The class loading strategy: 'self-first' (the default),
     * 'parent-first' (loads classes from the parent, then from the
     * extension) or 'plugin' (follows the rules from extensions
     * defined as plugins).
     */

  </description>
  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.plugin.resources.remote</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="remoteResourcesBundle">
      <name>RemoteResourcesBundle</name>
      <version>1.1.0</version>
      <description>Root element of the remote-resources.xml file.</description>

import org.jspecify.annotations.NullUnmarked;

/** Basic sanity tests for classes in {@code common.base}. */

@GwtIncompatible
@NullUnmarked
public class PackageSanityTests extends AbstractPackageSanityTests {
  public PackageSanityTests() {
    // package private classes like FunctionalEquivalence are tested through the public API.
    publicApiOnly();
  }