Select the product you need help with
BUG: You may receive an HTTP 405 "Method not allowed" error message when you browse the default document without specifying the file nameArticle ID: 216493 - View products that this article applies to. This article was previously published under Q216493 On This PageSYMPTOMSWhen you browse the default document, you receive one of the following error messages: HTTP Error 405 Method Not Allowed The method specified in the Request Line is not allowed for the resource identified by the request. Please ensure that you have the proper MIME type set up for the resource you are requesting. Please contact the server's administrator if this problem persists. HTTP 405 - Resource not allowed Internet Information Services
CAUSEThis problem occurs only when you use Microsoft Internet Information Services (IIS) 4.0 and Microsoft Internet Information Services 5.0. This problem occurs if you send a POST request to a server that is running IIS 4.0 or IIS 5.0, and the POST request contains a URL that ends in a slash mark (/). IIS returns the 405 error message instead of the default document. However, if the method value of the Verb property is GET or HEAD, IIS returns the default document. RESOLUTIONWhen the SOM is enabled and a DTC event is calledWhen the SOM is enabled for the page, a <FORM> tag that is similar to the following is inserted in the page.To work around this problem, use one of the following methods:
When the remote scripting is calledThis problem may occur if you use the window.location.href property in an HTML document to determine the path of the current document. If you do this when you initiate a remote scripting call, the remote scripting call fails because the client page does not have a file name.To determine whether the page can use remote scripting on the client, verify that the value of the window.location.href property does not end in a slash mark. To provide a file name in the client browser, and to prevent the error on the server, use the Response.Redirect method redirect the request from the default page to another page. For more information, see the first resolution method in the "" section. STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This bug was corrected in Microsoft Internet Information Services 6.0. PropertiesArticle ID: 216493 - Last Review: November 21, 2006 - Revision: 3.2
| Article Translations |


Back to the top








