Re: httpHandlers
- From: "John Timney \(MVP\)" <xyz_john@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Oct 2007 10:12:02 +0100
Might be one of those odd suggestions - but have you tried to just check the
request extension and drop through your handler if its missing or has an
..aspx extension?
Regards
John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"Manso" <Manso@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4D0B235D-78B2-4CD7-9B2D-A752081A57EB@xxxxxxxxxxxxxxxx
Hi,
We are doing custom request rewriting in a httpModule in
Application.AuthenticateRequest for requests coming in with .aspx using
HttpContext.RewritePath().
We are having a problem identifying requests that come in from registered
httpHandlers i.e. handlers with extension .aspx. These should just fall
through and not be analyzed/rewritten. Is there a way (flag?) that
identifies
a request as a request to a handler? The Context.CurrentHandler is not yet
set this early.
We could always read the configuration data but since handlers can be
added
further down in the config hierarchy we cannot cache it and it seems like
a
costly operation.
Grateful for any ideas.
Thanks,
Manso
.
- Follow-Ups:
- Re: httpHandlers
- From: Manso
- Re: httpHandlers
- Prev by Date: Re: Trace-Problem
- Next by Date: Re: httpresponse & redirect
- Previous by thread: Getting HTML of Web User Control
- Next by thread: Re: httpHandlers
- Index(es):
Relevant Pages
|
|