> 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/server/fr/knowledge-base/troubleshooting-articles/http-error-404.6-not-found-the-request-filtering-module-is-configured-to-deny-the-http-verb.md).

# HTTP Error 404.6 - Not Found, The request filtering module is configured to deny the HTTP verb

Corrige une erreur HTTP 404.6 dans Devolutions Server causée par le filtrage des requêtes IIS qui refuse un verbe HTTP, en activant l'autorisation des verbes non répertoriés dans le gestionnaire IIS.

Les DevTools du navigateur affichent l'erreur suivante lorsque des informations sont enregistrées dans le panneau d'administration de Devolutions Server :

```
HTTP Error 404.6 - Not Found
The request filtering module is configured to deny the HTTP verb.
```

#### Solution

Pour résoudre le problème, activez ***Autoriser les verbes non répertoriés*** dans les paramètres de ***Filtrage des demandes*** du gestionnaire IIS.

1. Ouvrez le gestionnaire IIS et accédez à votre site Devolutions Server.
2. Ouvrez ***Filtrage des demandes***.
3. Sélectionnez l'onglet ***Verbes HTTP***.
4. Dans le volet ***Actions***, cliquez sur ***Modifier les paramètres de la fonctionnalité...***
5. Activez ***Autoriser les verbes non répertoriés*** et cliquez sur ***OK***.
6. Réessayez l'action dans le panneau d'administration de Devolutions Server.

Une fois ***Autoriser les verbes non répertoriés*** activé, IIS devrait cesser de bloquer le verbe HTTP requis, et l'enregistrement des informations dans le panneau d'administration devrait fonctionner normalement.


---

# 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/server/fr/knowledge-base/troubleshooting-articles/http-error-404.6-not-found-the-request-filtering-module-is-configured-to-deny-the-http-verb.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.