First, I would like to know, if my application works perfectly under the development server comes with VS2005, does it mean I could successfully deploy my application under IIS (5.1) ? Or it is not always the case?
Second, I have the following configurations in my web.config file:
<httpHandlers>
<add verb="*" path="get" type="KiwiWebServer.AspCompatSTAHandler"/>
<add verb="*" path="default.aspx" type="KiwiWebServer.AspCompatSTAHandler"/>
<add verb="*" path="post" type="KiwiWebServer.AspCompatSTAHandler"/>
<add verb="*" path="logOut" type="KiwiWebServer.AspCompatSTAHandler"/>
</httpHandlers>
it works perfectly under the development server with vs 2005
but it doesn't work very well under IIS. IIS did transfer the request to default.aspx to my custom handler. but not the paths like "get", "post", or "logout"
instead it returns me the error 404 resource not found.
So which means the IIS 5.X or 6.0 can not deal with the requested files without extensions?
like in my case, the full URL is
http://localhost/get?page=home
the IIS was unable to route the requests to my handler class, instead gives me the 404.
anyone can help?
Cheers
Tony
My application is XML based, customized the web application, It only contains the default.aspx page. I generate the rest by my application. So I have to redirect all the requests such like
http://localhost/XXX/get?page=home to my handler to handle it.
Can someone help please?