Rewrite rule do not work for long URLs in IIS

Question

I am using IIS as reverse proxy that redirects traffic made to some domain name like domain.com to internal kestrel service at localhost:5000. I am using regular expression (.*) and I am redirecting that to localhost:5000/{R:1}. This works perfectly fine, but not for one case of the application.

There is one case when very long url is created (855 characters) and then I am receiving bellow response:

The same url copy pasted to localhost:5000 works fine.

I realized that when I remove (approximately) half/ more than half of the url I am receiving another response:

When I check service logs I see that first request do not went through to the application while second was logged, so I assume that request with full url was not redirected at all.

When I click test rule in IIS I see that this window is also cutting the url

Are my assumptions correct? Is there any way to make it works?

Answer 1

HTTP requests are initially processed by http.sys and can be rejected at this stage before reaching the IIS pipelines.

This explains why you saw that 400 error page, even if you configured rewrite rules and the execution of URL rewrite rules is at the start of the pipelines.

Answer 2

@Zimon, Robert

HTTP Error 400 happens when a server cannot understand a request that's been made of it. In your situation, the reason of Bad request error is invalid URL. You can try to Increase Query String and URL Length Limit in IIS.

1. Open the site in IIS and double click the Request Filtering module.
2. Click the Query Strings, then right click in the white area shown below then click the context menu option called Edit Feature Setting.

3. change the value of Maximum URL length and Maximum query string to something more appropriate for your needs.

You can refer to here and here to know about the Element for request limits.

Best regards,

Jinlei Shuang

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread