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

Fixes an HTTP 404.6 error in Devolutions Server caused by IIS request filtering denying an HTTP verb by enabling allow unlisted verbs in IIS Manager.

The browser DevTools displays the following error when information is saved in the Devolutions Server administration panel:

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

#### Solution

To resolve the issue, enable ***Allow unlisted verbs*** in the ***Request Filtering*** settings in IIS Manager.

1. Open IIS Manager and navigate to your Devolutions Server site.
2. Open ***Request Filtering***.
3. Select the ***HTTP Verbs*** tab.
4. In the ***Actions*** pane, click ***Edit Feature Settings...***
5. Enable ***Allow unlisted verbs*** and click ***OK***.
6. Retry the action in the Devolutions Server administration panel.

Once ***Allow unlisted verbs*** is enabled, IIS should stop blocking the required HTTP verb, and saving information in the administration panel should work normally.


---

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