«

Hello,
I try to use a custom HttpHandler to add something to session, then display
the original page.

public void ProcessRequest(HttpContext context)
{
context.Session["test"] = "test";
}

But, a empty page is rendered with this HttpHandler, should I add some
additional codes to ProcessRequest to make it display the page correctly.

Thanks

Page itself is sample of existing Httphandler, so your code doesn't really
do anything else that the code shows (Page's equivalent implementation
contains dealing with page lifecycle etc etc, a ton of logic) Maybe you want
to redirect to the correct page? With

context.Server.Transfer("page.aspx");

Anyways, if your intention is to add some logic to the http application
lifecycle instead of replacing the original HttpHandler, you'd want to use
an HTTP Module

--
Teemu Keiski
AspInsider, ASP.NET MVP
http://blogs.aspadvice.com/joteke
http://teemukeiski.net


"zlf" <> wrote in message
news:eOX90da$...
> Hello,
> I try to use a custom HttpHandler to add something to session, then
> display the original page.
>
> public void ProcessRequest(HttpContext context)
> {
> context.Session["test"] = "test";
> }
>
> But, a empty page is rendered with this HttpHandler, should I add some
> additional codes to ProcessRequest to make it display the page correctly.
>
> Thanks
>

So it is impossible to add some logic before showing page using HttpHandler?
Thanks

"Teemu Keiski" <> дÈëÏûÏ¢ÐÂÎÅ:%233wVK1a$ bl...
> Page itself is sample of existing Httphandler, so your code doesn't really
> do anything else that the code shows (Page's equivalent implementation
> contains dealing with page lifecycle etc etc, a ton of logic) Maybe you
> want to redirect to the correct page? With
>
> context.Server.Transfer("page.aspx");
>
> Anyways, if your intention is to add some logic to the http application
> lifecycle instead of replacing the original HttpHandler, you'd want to use
> an HTTP Module
>
> --
> Teemu Keiski
> AspInsider, ASP.NET MVP
> http://blogs.aspadvice.com/joteke
> http://teemukeiski.net
>
>
> "zlf" <> wrote in message
> news:eOX90da$...
>> Hello,
>> I try to use a custom HttpHandler to add something to session, then
>> display the original page.
>>
>> public void ProcessRequest(HttpContext context)
>> {
>> context.Session["test"] = "test";
>> }
>>
>> But, a empty page is rendered with this HttpHandler, should I add some
>> additional codes to ProcessRequest to make it display the page correctly.
>>
>> Thanks
>>
>
>

An HttpHandler isn't a "page" - it's a lightweight request handler without
all the baggage of the Page Class. You could redirect or do a Server.Transfer
to an actual ASPX page after you do your "stuff" in the handler.
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com



"zlf" wrote:

> So it is impossible to add some logic before showing page using HttpHandler?
> Thanks
>
> "Teemu Keiski" <> �´Èë�û�¢�ÂÎÅ:%233wVK1a$HHA.4476@TK2MSF TNGP06.phx.gbl...
> > Page itself is sample of existing Httphandler, so your code doesn't really
> > do anything else that the code shows (Page's equivalent implementation
> > contains dealing with page lifecycle etc etc, a ton of logic) Maybe you
> > want to redirect to the correct page? With
> >
> > context.Server.Transfer("page.aspx");
> >
> > Anyways, if your intention is to add some logic to the http application
> > lifecycle instead of replacing the original HttpHandler, you'd want to use
> > an HTTP Module
> >
> > --
> > Teemu Keiski
> > AspInsider, ASP.NET MVP
> > http://blogs.aspadvice.com/joteke
> > http://teemukeiski.net
> >
> >
> > "zlf" <> wrote in message
> > news:eOX90da$...
> >> Hello,
> >> I try to use a custom HttpHandler to add something to session, then
> >> display the original page.
> >>
> >> public void ProcessRequest(HttpContext context)
> >> {
> >> context.Session["test"] = "test";
> >> }
> >>
> >> But, a empty page is rendered with this HttpHandler, should I add some
> >> additional codes to ProcessRequest to make it display the page correctly.
> >>
> >> Thanks
> >>
> >
> >
>
>
>

Let's take a example, if we set <add verb="*" path="*.aspx"
type="CustomHandler,HandlerAssembly"/>, at do
context.Response.Redirect(context.Request.Url.Abso lutePath) in
ProcessRequest(HttpContext context). The context.Response.Redirect will be
handled by CustomHandler again, so that will lead to a infinite loop. Do I
make some mistake?

Thanks

"Peter Bromberg [C# MVP]" <> дÈëÏûÏ¢ÐÂÎÅ:EAD73C68-839F-40AE-A55C-...
> An HttpHandler isn't a "page" - it's a lightweight request handler without
> all the baggage of the Page Class. You could redirect or do a
> Server.Transfer
> to an actual ASPX page after you do your "stuff" in the handler.
> -- Peter
> Recursion: see Recursion
> site: http://www.eggheadcafe.com
> unBlog: http://petesbloggerama.blogspot.com
> BlogMetaFinder: http://www.blogmetafinder.com
>
>
>
> "zlf" wrote:
>
>> So it is impossible to add some logic before showing page using
>> HttpHandler?
>> Thanks
>>
>> "Teemu Keiski" <> D¡ä¨¨????¡éD???:%233wVK1a$ x.gbl...
>> > Page itself is sample of existing Httphandler, so your code doesn't
>> > really
>> > do anything else that the code shows (Page's equivalent implementation
>> > contains dealing with page lifecycle etc etc, a ton of logic) Maybe you
>> > want to redirect to the correct page? With
>> >
>> > context.Server.Transfer("page.aspx");
>> >
>> > Anyways, if your intention is to add some logic to the http application
>> > lifecycle instead of replacing the original HttpHandler, you'd want to
>> > use
>> > an HTTP Module
>> >
>> > --
>> > Teemu Keiski
>> > AspInsider, ASP.NET MVP
>> > http://blogs.aspadvice.com/joteke
>> > http://teemukeiski.net
>> >
>> >
>> > "zlf" <> wrote in message
>> > news:eOX90da$...
>> >> Hello,
>> >> I try to use a custom HttpHandler to add something to session, then
>> >> display the original page.
>> >>
>> >> public void ProcessRequest(HttpContext context)
>> >> {
>> >> context.Session["test"] = "test";
>> >> }
>> >>
>> >> But, a empty page is rendered with this HttpHandler, should I add some
>> >> additional codes to ProcessRequest to make it display the page
>> >> correctly.
>> >>
>> >> Thanks
>> >>
>> >
>> >
>>
>>
>>

Resolved, do something like the following in ProcessRequest will be ok.
Thanks

string aspxPagePath = rawUrl.Substring(0,
rawUrl.IndexOf(".aspx") + 5);
IHttpHandler handler =
PageParser.GetCompiledPageInstance(aspxPagePath, null, context);
// Process the page just like any other aspx page
handler.ProcessRequest(context);

"zlf" <> дÈëÏûÏ¢ÐÂÎÅ:%23UP24El$ l...
> Let's take a example, if we set <add verb="*" path="*.aspx"
> type="CustomHandler,HandlerAssembly"/>, at do
> context.Response.Redirect(context.Request.Url.Abso lutePath) in
> ProcessRequest(HttpContext context). The context.Response.Redirect will be
> handled by CustomHandler again, so that will lead to a infinite loop. Do I
> make some mistake?
>
> Thanks
>
> "Peter Bromberg [C# MVP]" <> дÈëÏûÏ¢ÐÂÎÅ:EAD73C68-839F-40AE-A55C-...
>> An HttpHandler isn't a "page" - it's a lightweight request handler
>> without
>> all the baggage of the Page Class. You could redirect or do a
>> Server.Transfer
>> to an actual ASPX page after you do your "stuff" in the handler.
>> -- Peter
>> Recursion: see Recursion
>> site: http://www.eggheadcafe.com
>> unBlog: http://petesbloggerama.blogspot.com
>> BlogMetaFinder: http://www.blogmetafinder.com
>>
>>
>>
>> "zlf" wrote:
>>
>>> So it is impossible to add some logic before showing page using
>>> HttpHandler?
>>> Thanks
>>>
>>> "Teemu Keiski" <> D¡ä¨¨????¡éD???:%233wVK1a$ x.gbl...
>>> > Page itself is sample of existing Httphandler, so your code doesn't
>>> > really
>>> > do anything else that the code shows (Page's equivalent implementation
>>> > contains dealing with page lifecycle etc etc, a ton of logic) Maybe
>>> > you
>>> > want to redirect to the correct page? With
>>> >
>>> > context.Server.Transfer("page.aspx");
>>> >
>>> > Anyways, if your intention is to add some logic to the http
>>> > application
>>> > lifecycle instead of replacing the original HttpHandler, you'd want to
>>> > use
>>> > an HTTP Module
>>> >
>>> > --
>>> > Teemu Keiski
>>> > AspInsider, ASP.NET MVP
>>> > http://blogs.aspadvice.com/joteke
>>> > http://teemukeiski.net
>>> >
>>> >
>>> > "zlf" <> wrote in message
>>> > news:eOX90da$...
>>> >> Hello,
>>> >> I try to use a custom HttpHandler to add something to session, then
>>> >> display the original page.
>>> >>
>>> >> public void ProcessRequest(HttpContext context)
>>> >> {
>>> >> context.Session["test"] = "test";
>>> >> }
>>> >>
>>> >> But, a empty page is rendered with this HttpHandler, should I add
>>> >> some
>>> >> additional codes to ProcessRequest to make it display the page
>>> >> correctly.
>>> >>
>>> >> Thanks
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>
>