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

Behebt einen HTTP 404.6-Fehler in Devolutions Server, der durch die IIS-Anforderungsfilterung verursacht wird, die ein HTTP-Verb verweigert, indem nicht aufgelistete Verben im IIS-Manager zugelassen w

Die DevTools des Browsers zeigen den folgenden Fehler an, wenn Informationen im Administrationsbereich von Devolutions Server gespeichert werden:

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

#### Lösung

Um das Problem zu beheben, aktivieren Sie ***Allow unlisted verbs*** in den Einstellungen der ***Request Filtering*** im IIS-Manager.

1. Öffnen Sie den IIS-Manager und navigieren Sie zu Ihrer Devolutions Server-Website.
2. Öffnen Sie ***Request Filtering***.
3. Wählen Sie die Registerkarte ***HTTP Verbs*** aus.
4. Klicken Sie im Bereich ***Actions*** auf ***Edit Feature Settings...***
5. Aktivieren Sie ***Allow unlisted verbs*** und klicken Sie auf ***OK***.
6. Wiederholen Sie die Aktion im Administrationsbereich von Devolutions Server.

Sobald ***Allow unlisted verbs*** aktiviert ist, sollte IIS das erforderliche HTTP-Verb nicht mehr blockieren, und das Speichern von Informationen im Administrationsbereich sollte normal funktionieren.


---

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