And for those wondering why I'd rather rewrite the app than to pursue changes through NS. There is the thread from their support forums. Perhaps my original post did not describe the issue, but I'm pretty sure I didn't ask anything about the
error page. I do suppose I could be clever with 404 handling using a custom page that parses out the desired URL and looks up the proper PostId and such.
In the reply, I'm impressed that the guy actually looked at my account, though he didn't note that child folders already override the error mode setting in their own web.config files.
QUOTE (FatNoah @ May 29 2009, 01:01 AM)
<!--quotec-->I am trying to deploy an application that uses URL rewriting. Specifically, I have an HTTP module is registered in the web.config that looks at a request for pages and "rewrites' the requests to go to another page.
For example, the URL for a blog post is really Post.aspx?id=[SOME_GUID], but with URL rewriting I can create a link to a non-existant ASPX page such as MyFirstPost.aspx that is more "user friendly." Even though this page doesn't exist, users going
to the page won't get a 404 because the url will be rewritten to Post.aspx?id=[SOME_GUID].
The problem I am having is with an IIS setting that isn't configurable through the web.config for IIS 6. This setting tells IIS to verify that file exists before handing the request off to the ASP.NET ISAPI. It appears this setting is On, which means that requests
for my "user friendly" URLs are not passed on to ASP.NET by IIS.
Fixing this is simply a matter of unchecking a box in an IIS application configuration screen, but does anyone know if Network Solutions will make such a change? If so, does anyone have any suggestions on how to phrase my request so that the support tech handling
it will know what I'm asking?
Actually, this is already enabled, and you can make custom 404 pages using web.config.
Your specific issue is caused because of line 45 in your web.config
Change this to point your specific custom error page and it will work.
<error statusCode="404" redirect="/kristenandnoah/error404.aspx" />
I see you're trying to have different custom error pages for different folders, and this may be where your frustration is coming in. Except for applications that were auto-installed from within the Open Source section of the Hosting Manager, we only support
one .net application per hosting package, and it must be located in the /htdocs folder.
You may need to be more creative with your error.aspx script if you are looking for an error page that varies depending on URL used. <!--IBF.ATTACHMENT_19013-->