> 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/es/plataforma/middleware.md).

# Middleware

Personalice las solicitudes HTTP en PowerShell Universal mediante scripts de middleware que modifican códigos de estado, encabezados y cookies antes de que se complete cada solicitud.

El middleware se ejecuta durante cada solicitud HTTP por parte del servidor de PowerShell Universal. Le brinda la oportunidad de personalizar funciones de la solicitud como el código de estado, los encabezados y las cookies.

{% hint style="warning" %}
Dado que el middleware se ejecuta durante cada solicitud, se debe tener en cuenta el rendimiento al implementar middleware personalizado.
{% endhint %}

### Middleware.ps1

El fichero middleware.ps1 puede crearse en la carpeta `.universal` mediante el cmdlet `New-PSUMiddleware`.

Cada instancia de middleware recibe un objeto [HttpContext](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/use-http-context?view=aspnetcore-7.0) cuando se le llama. El middleware debe devolver true o false. Si se devuelve false, el middleware dejará de pasar el contexto a los elementos adicionales de la canalización de middleware.

El siguiente ejemplo añade una cookie de prueba a la respuesta.

```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/es/plataforma/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.