> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/de/plattform/middleware.md).

# Middleware

Passen Sie HTTP-Anfragen in PowerShell Universal mithilfe von Middleware-Skripten an, die Statuscodes, Header und Cookies vor Abschluss jeder Anfrage ändern.

Middleware wird vom PowerShell Universal-Server bei jeder HTTP-Anfrage ausgeführt. Sie bietet Ihnen die Möglichkeit, Funktionen der Anfrage wie Statuscode, Header und Cookies anzupassen.

{% hint style="warning" %}
Da Middleware bei jeder Anfrage ausgeführt wird, sollte die Leistung bei der Implementierung benutzerdefinierter Middleware berücksichtigt werden.
{% endhint %}

### Middleware.ps1

Die Datei middleware.ps1 kann im Ordner `.universal` mit dem Cmdlet `New-PSUMiddleware` erstellt werden.

Jede Middleware-Instanz erhält beim Aufruf ein [HttpContext](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/use-http-context?view=aspnetcore-7.0)-Objekt. Die Middleware sollte true oder false zurückgeben. Wenn false zurückgegeben wird, gibt die Middleware den Kontext nicht mehr an weitere Elemente in der Middleware-Pipeline weiter.

Das folgende Beispiel fügt der Antwort ein Test-Cookie hinzu.

```powershell
New-PSUMiddleware -Name 'Middle' -ScriptBlock {
    param($HttpContext)
    $HttpContext.Response.Cookies.Append('X-Test', "Test")
    $true
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/de/plattform/middleware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.