> 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/fr/plateforme/middleware.md).

# Middleware

Personnalisez les requêtes HTTP dans PowerShell Universal à l'aide de scripts middleware qui modifient les codes de statut, les en-têtes et les témoins avant la fin de chaque requête.

Le middleware est exécuté à chaque requête HTTP par le serveur PowerShell Universal. Il vous donne l'occasion de personnaliser des fonctionnalités de la requête comme le code de statut, les en-têtes et les témoins.

{% hint style="warning" %}
Puisque le middleware est exécuté à chaque requête, la performance devrait être prise en considération lors de l'implémentation d'un middleware personnalisé.
{% endhint %}

### Middleware.ps1

Le fichier middleware.ps1 peut être créé dans le dossier `.universal` à l'aide de l'applet de commande `New-PSUMiddleware`.

Chaque instance de middleware reçoit un objet [HttpContext](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/use-http-context?view=aspnetcore-7.0) lorsqu'elle est appelée. Le middleware devrait retourner true ou false. Si false est retourné, le middleware cessera de transmettre le contexte aux éléments additionnels du pipeline de middleware.

L'exemple ci-dessous ajoute un témoin de test à la réponse.

```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/fr/plateforme/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.