IIS 7 and Above
URL Rewrite Module
rewrite causing 500 errors
Last post Mar 04, 2020 02:43 AM by Jalpa Panchal
Feb 04, 2020 02:02 PM|stevelogan|LINK
IIS 10, Windows 2K16, URL Rewrite 2.1. The server has about 6 sites on it, 2 of which us rewrite rules. Site #1 ran fine with it's rewrite rules until about 2 weeks ago when it would start go give random 500 errors. We enabled failed request tracing which
shows the error below. When we disable the rules and access the URL directly, the error goes away, which is what we did on site #1. #2 is our API and is a bit more complex to just eliminate the rules from. The rewrite rules look like this:
All other sites that do not use rewrite in URL rewrite (we have some redirct rules but they're not effected) work fine. The API site also works fine on a different, identical server. At this point I'm out of ideas as to where to even look. Tomcat indicates
an IIS issue, IIS support people say it's a Tomcat issue etc.
Feb 04, 2020 07:16 PM|Rovastar|LINK
Well the error seems to be in the isapi_redirect.dll which is a Tomcat redirection dll.
Which for me it is in their camp.
It seems like using the Microsofts URLrewrite module is probably changing something before it get there and the Tom redirect dll doesn't understand it.
Compare the details (in failed request tracing) in the request after it has done the URLrewrite part to a request when you have disabled the rule.
I expect suitable differences there,
Feb 05, 2020 08:17 AM|Jalpa Panchal|LINK
This is the tomcat related issue. you could try to use the arr instead of the tomcat redirector. The error code ERROR_INVALID_FUNCTION is generated by the ISAPI filter.
you could also try to follow this below article:
Mar 04, 2020 02:43 AM|Jalpa Panchal|LINK
Is your issue solved?
If your issue is solved then I request you to mark the helpful suggestion as an answer. This will help other people who face the same issue.
If your issue still exists then try to refer the solution given by the community members.
If then also you have any further questions then let us know about it.
We will try to provide further suggestions to solve the issue.
Thanks for your understanding.