ASP.NET

Jkirt15-Jun-07 4:01

15-Jun-07 4:01

Ben,

Thank you for the prompt reply. I have enabled the default content page in IIS and it's pointing to index.aspx. I do want the default page to be index.aspx.

The thing is, I've designed user friendly urls but they won't work because IIS is trying to go directly to them but they are virtual, so they don't exist. I'm using HttpContext.RewritePath to rewrite the urls.

Jason.

kubben15-Jun-07 4:12

15-Jun-07 4:12

So if the user types in the base url with no page, it will go to your default page. So what is your problem? I have done much RewritePath stuff, but I have done some http handler stuff. Are you sure your handler is set up correctly so that it is getting called?

Ben

Jkirt15-Jun-07 4:59

15-Jun-07 4:59

I think you might be misunderstanding my problem. Let's say my root directory has only the following files:

* index.aspx
* web.config
* global.asax

When the user visits, for example: http://www.mysite.com/tutorials/tute/1

The global.asax file should be able to grab this URL using HttpContext.Current.Request.Url.AbsolutePath.ToLower method and I will use this string to formulate a RewritePath to index.aspx?a=tutorials&tute=1.

As you can see, the directories tutorials, tute and 01 don't exist, so there is no index.aspx file to refer to.

My problem is, IIS and HttpContext.AbsolutePath isn't giving me http://www.mysite.com/tutorials/tute/1 or any of the variables. But the strange thing is, this is all working on localhost.

So it makes me wonder if it's something to do with IIS, or if there is another way to get the typed URL.

Jason.

kubben15-Jun-07 5:13

15-Jun-07 5:13

Well, if IIS is trying to correct the url and re-direct it to your default page, then you there is probably only one thing you can do. Turn off the default page in IIS and then you will have to write an http handler module for the 404 and properly redirect them. At least that is what I would try to do.

Ben

Jkirt15-Jun-07 5:52

15-Jun-07 5:52

Thanks for the suggestions Ben, but I can't turn off the default pages because I can't guarantee every visitor will use http://www.mysite.com/tutorials/tute/1, they may access via http://www.mysite.com.

Also, doesn't Application_beginRequest execute before it delivers a page? I have code that works (and I know it does because I've tried hard coding a string in place of the return value of HttpContext.Current.Request.Url.AbsolutePath.ToLower and tested on IIS), I just need to get the URL of page before IIS decides to throw a 404.

Ugh, what's going on with IIS?!
-.-..

Jason

kubben15-Jun-07 6:02

15-Jun-07 6:02

There must be something going on with your setup. I just tried one of my site putting in a virtual dir that doesn't exist and I get the 404 message. So, do you have an error page set up? Or something like that? According to MS help:
The following events are executed by the HttpApplication class while the request is processed. The events are of particular interest to developers who want to extend the HttpApplication class.

Validate the request, which examines the information sent by the browser and determines whether it contains potentially malicious markup. For more information, see ValidateRequest and Script Exploits Overview.

Perform URL mapping, if any URLs have been configured in the UrlMappingsSection section of the Web.config file.

Raise the BeginRequest event.

Raise the AuthenticateRequest event.

Raise the PostAuthenticateRequest event.

Raise the AuthorizeRequest event.

Raise the PostAuthorizeRequest event.

Raise the ResolveRequestCache event.

Raise the PostResolveRequestCache event.

Based on the file name extension of the requested resource (mapped in the application's configuration file), select a class that implements IHttpHandler to process the request. If the request is for an object (page) derived from the Page class and the page needs to be compiled, ASP.NET compiles the page before creating an instance of it.

Raise the PostMapRequestHandler event.

Raise the AcquireRequestState event.

Raise the PostAcquireRequestState event.

Raise the PreRequestHandlerExecute event.

Call the ProcessRequest method (or the asynchronous version BeginProcessRequest) of the appropriate IHttpHandler class for the request. For example, if the request is for a page, the current page instance handles the request.

Raise the PostRequestHandlerExecute event.

Raise the ReleaseRequestState event.

Raise the PostReleaseRequestState event.

Perform response filtering if the Filter property is defined.

Raise the UpdateRequestCache event.

Raise the PostUpdateRequestCache event.

Raise the EndRequest event.

Anyway, don't know if that helps or not.

Ben

Jkirt15-Jun-07 6:11

15-Jun-07 6:11

Err.. not really, I don't understand IIS well enough or to that level.
Thanks anyway.

Jason

kubben15-Jun-07 6:03

15-Jun-07 6:03

Here is some more MS help:
Raised at the appropriate time in the application life cycle, as listed in the application life cycle table earlier in this topic.

Application_Error can be raised at any phase in the application life cycle.

Application_EndRequest is the only event that is guaranteed to be raised in every request, because a request can be short-circuited. For example, if two modules handle the Application_BeginRequest event and the first one throws an exception, the Application_BeginRequest event will not be called for the second module. However, the Application_EndRequest method is always called to allow the application to clean up resources.

So if you do have an error handling page it might be causing the problem.

Ben

Jkirt15-Jun-07 6:18

15-Jun-07 6:18

I do have a dud error handling page, but did not originally; and it still wasn't working.
I only added it because I was desperate and tried this.
"On IIS 6.0 change 404 default page to /404.aspx and the type to "URL"."

Jason

Jkirt15-Jun-07 19:35