> 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/it/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

Risolve un errore HTTP 404.6 in Devolutions Server causato dal filtraggio delle richieste di IIS che nega un verbo HTTP, abilitando la consentita dei verbi non elencati in Gestione IIS.

Gli strumenti di sviluppo (DevTools) del browser mostrano il seguente errore quando le informazioni vengono salvate nel pannello di amministrazione di Devolutions Server:

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

#### Soluzione

Per risolvere il problema, abiliti ***Consenti verbi non elencati*** nelle impostazioni di ***Filtro richieste*** in Gestione IIS.

1. Apra Gestione IIS e vada al suo sito Devolutions Server.
2. Apra ***Filtro richieste***.
3. Selezioni la scheda ***Verbi HTTP***.
4. Nel riquadro ***Azioni***, faccia clic su ***Modifica impostazioni funzionalità...***
5. Abiliti ***Consenti verbi non elencati*** e faccia clic su ***OK***.
6. Riprovi l'azione nel pannello di amministrazione di Devolutions Server.

Una volta abilitata l'opzione ***Consenti verbi non elencati***, IIS dovrebbe smettere di bloccare il verbo HTTP richiesto e il salvataggio delle informazioni nel pannello di amministrazione dovrebbe funzionare normalmente.


---

# 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/it/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.