IIS 7 and Above
URL Rewrite Module
405 error - HTTP verb used to access this page is not allowed
Last post Feb 13, 2018 07:25 AM by Yuk Ding
Feb 07, 2018 11:32 PM|KaneW|LINK
After spending whole day to fix why my test client cannot access to the internal web server, there is another 405 error come up. I hope some of you can help.
I am using rewrite rule to forward my url from http:\\www.company.com\app1 to
http://app1.company.local:8080. I can see the page show up but there are some problem found.
2. after enter the user name and password, it goes to the next page but display "405 error - HTTP verb used to access this page is not allowed" error.
After talking to my web developer, I was told, the site is usign ASP .net with MVC and using Controller -> Method -> record ID in web application.
When I use Failed Request Tracing tool, I spot two things.
1. In Condition Evaluation, I have this feedback..
But when I type
http://www.company.com/app1, I can go to the correct site at
After enter my user name and password for the internal app, I received error 405.
HttpReason Method Not Allowed
ErrorCode Incorrect function.
What do I need to fix the issue?
Feb 08, 2018 09:04 AM|Yuk Ding|LINK
The problem is static file should not be used to handle the request with credential. So please ensure you have published the MVC to IIS correctly and IIS asp.net development feature has been enabled via turn windows features on or off/add role and feature.
Secondly, please ensure your handler allow the post/get verb. You could set it in IIS manager->site level->handler mapping->select handler->edit feature permission->require restriction->verb.
Please ensure you have deployed the mvc application following this link:
In addition, please ensure your asp.net handler have higher priority to execute the request than staticcontent handler.
It really looks like your MVC route is not working.
Feb 08, 2018 05:13 PM|KaneW|LINK
Thanks for your response and suggestion. Can you give me more information about the "handler" setting, should it be configured on ARR server, or the actual IIS server which host the web application? Also, whenn publish the MVC to IIS, this IIS is also my
ARR server or the actual web application IIS server.
In the meanwhile, I will go through the provided link with my web app developer.
Feb 09, 2018 09:48 AM|Yuk Ding|LINK
Where you could find the 405 error in IIS log, then you should go to to this server and set the configuration. Most of time , I think it should come from the backend IIS server.
Do you have extensionlessURlHandler in your handler mapping? This should be used to handle the url instead of staticcontent handler.
Feb 09, 2018 05:26 PM|KaneW|LINK
Thank you for your response Yuk;
I went to the IIS server which is hosting the actual web application, I check the ExtensionlessUrlHandler in Handler Mapping and here is what I found...
Name Path State Path Type Handler Entry Type
ExtensionlessUrlHandler-Integrated-4.0 * Enabled Unspecified System.Web.Handlers.Transfer Inherited
ExtensionlessUrlHandler-ISAPI-4.0-32-bit * Enabled Unspecified IsapiModule Inherited
ExtensionlessUrlHandler-ISAPI-4.0-64-bit * Enabled Unspecified IsapiModule Inherited
Feb 13, 2018 07:25 AM|Yuk Ding|LINK
If the asp.net feature has been installed.Then static file handler should not handle the application unless you didn't deploy the asp.net application correctly.