Re: Custom HttpHandler and Server.Transfer



Hi Bryan,

Of course Context.RewritePath is a serverside operation which change the
server side processing path for the current request. No roundtrip to client
(the browser's address bar will remain the original one....). Usuallly it
is used for Url Rewriting in asp.net application (to provide static look
url which is search engine friendly...). Here is a article discuss this:

#URL Rewriting in ASP.NET
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html
/urlrewriting.asp

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

--------------------
| From: bryan@xxxxxxxxxxxxxxxxx
| Subject: Re: Custom HttpHandler and Server.Transfer
| Date: Tue, 27 Dec 2005 07:37:55 -0600
| Message-ID: <6pg2r15c20o9t1bp1a26fudbft5onmv6t6@xxxxxxx>
| References: <6acpq1h5lhpljps8k1u1vhuicadj5s5crg@xxxxxxx>
<bBKS58cCGHA.3992@xxxxxxxxxxxxxxxxxxxxx>
<e510r11pfkrbpl9me3fsrgm4u3ut9g7ksv@xxxxxxx>
<NujKeXqCGHA.1424@xxxxxxxxxxxxxxxxxxxxx>
| X-Newsreader: Forte Agent 3.1/32.783
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: adsl-68-253-212-158.dsl.emhril.ameritech.net
68.253.212.158
| Lines: 1
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet:367136
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Steven-
| Will rewrite path cause the transfer to handled entirely on the
| server, or will it still cause anther round trip to the client and
| back?
|
| Thanks again for all the help.
|
| Cheers,
| Bryan
|
| On Tue, 27 Dec 2005 05:24:45 GMT, stcheng@xxxxxxxxxxxxxxxxxxxx (Steven
| Cheng[MSFT]) wrote:
|
| >Hi Bryan,
| >
| >Thanks for your response. I've just performed some further test
according
| >to your scenario, I did reproduce the problem you encountered, and after
| >some further research, it seems due to the HttpServerUtility.Transfer
| >methods only addressing transfer to another Page handler, I've check the
| >related code and found that when the runtime found the target handler is
| >not a page hanlder, it'll throw exception....
| >
| >So far, in addition to use Response.Redirect, you can also have a look
at
| >the HttpContext.RewritePath method which can help forward the internal
| >request to another resource in same application,e.g:
| >
| > if(context.Request.QueryString["transfer"] != null)
| > {
| > context.RewritePath("test.sh?id=aa&test=bb&asp=111");
| > }
| >
| >Thanks & Regards,
| >
| >Steven Cheng
| >Microsoft Online Support
| >
| >Get Secure! www.microsoft.com/security
| >(This posting is provided "AS IS", with no warranties, and confers no
| >rights.)
| >
| >
| >--------------------
| >| From: bryan@xxxxxxxxxxxxxxxxx
| >| Subject: Re: Custom HttpHandler and Server.Transfer
| >| Date: Mon, 26 Dec 2005 08:59:31 -0600
| >| Message-ID: <e510r11pfkrbpl9me3fsrgm4u3ut9g7ksv@xxxxxxx>
| >| References: <6acpq1h5lhpljps8k1u1vhuicadj5s5crg@xxxxxxx>
| ><bBKS58cCGHA.3992@xxxxxxxxxxxxxxxxxxxxx>
| >| X-Newsreader: Forte Agent 3.1/32.783
| >| MIME-Version: 1.0
| >| Content-Type: text/plain; charset=us-ascii
| >| Content-Transfer-Encoding: 7bit
| >| Newsgroups: microsoft.public.dotnet.framework.aspnet
| >| NNTP-Posting-Host: adsl-68-253-212-158.dsl.emhril.ameritech.net
| >68.253.212.158
| >| Lines: 1
| >| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| >| Xref: TK2MSFTNGXA02.phx.gbl
| >microsoft.public.dotnet.framework.aspnet:367058
| >| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| >|
| >| Steven -
| >| Thanks for the reply. The target of the Transfer is another page in
| >| the same app that should be handled by the same custom handler. The
| >| custom extension is set so that the handler gets invoked even if the
| >| "pages" are not pesent, and there is in fact no physical page for the
| >| target (nor is there for the source.)
| >|
| >| Cheers,
| >| Bryan
| >|
| >| On Mon, 26 Dec 2005 03:48:16 GMT, stcheng@xxxxxxxxxxxxxxxxxxxx (Steven
| >| Cheng[MSFT]) wrote:
| >|
| >| >Hi Bryan,
| >| >
| >| >As for ASP.NET's Server.Transfer method, it can only help forward
| >request
| >| >between the pages or urls within the same asp.net webapplcation, we
can
| >not
| >| >use Server.Transfer to direct the current request to a resource in
| >| >different application or on other server. So what's the url you used
in
| >the
| >| >Server.Transfer ?
| >| >
| >| >Regards,
| >| >
| >| >Steven Cheng
| >| >Microsoft Online Support
| >| >
| >| >Get Secure! www.microsoft.com/security
| >| >(This posting is provided "AS IS", with no warranties, and confers no
| >| >rights.)
| >| >
| >| >
| >| >--------------------
| >| >| From: bryan@xxxxxxxxxxxxxxxxx
| >| >| Subject: Custom HttpHandler and Server.Transfer
| >| >| Date: Fri, 23 Dec 2005 20:27:01 -0600
| >| >| Message-ID: <6acpq1h5lhpljps8k1u1vhuicadj5s5crg@xxxxxxx>
| >| >| X-Newsreader: Forte Agent 3.1/32.783
| >| >| MIME-Version: 1.0
| >| >| Content-Type: text/plain; charset=us-ascii
| >| >| Content-Transfer-Encoding: 7bit
| >| >| Newsgroups: microsoft.public.dotnet.framework.aspnet
| >| >| NNTP-Posting-Host: adsl-68-253-212-158.dsl.emhril.ameritech.net
| >| >68.253.212.158
| >| >| Lines: 1
| >| >| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| >| >| Xref: TK2MSFTNGXA02.phx.gbl
| >| >microsoft.public.dotnet.framework.aspnet:366884
| >| >| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| >| >|
| >| >| I've got a custom HttpHandler to process all requests for a given
| >| >| extension. It gets invoked OK, but if I try to do a Server.Transfer
I
| >| >| get an HttpException. A Response.Redirect works, but I really need
to
| >| >| avoid the extra round-trip to the client.
| >| >|
| >| >| I've tried Passing the page name, the full URL, and the instance of
| >| >| the handler class to the Transfer method, but everything gets me the
| >| >| same error 500.
| >| >|
| >| >| Any help would be appreciated.
| >| >|
| >| >| Thanks,
| >| >| Bryan
| >| >|
| >|
|

.



Relevant Pages

  • AJAX simultaneous requests getting queued up
    ... server for updated information to show, ... Handler, ... Once the first request comes back, ... To make sure the problem wasn't on the client, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Custom HttpHandler and Server.Transfer
    ... methods only addressing transfer to another Page handler, ... request to another resource in same application,e.g: ... | Subject: Re: Custom HttpHandler and Server.Transfer ... |>Hi Bryan, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Strange test results on IIS6 when 404 set to custom ASP redirect
    ... using a separate HTTP request by the client to the server. ... then the 404 handler is invoked. ... >> checklink validator) is making requests to your website, ...
    (microsoft.public.inetserver.iis)
  • Re: Custom HttpHandler and Server.Transfer
    ... >Hi Bryan, ... >methods only addressing transfer to another Page handler, ... >request to another resource in same application,e.g: ... >| Subject: Re: Custom HttpHandler and Server.Transfer ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: http handlers
    ... In order for you handler to run the IIS must send request through ASP.NET engine. ... Though when I try to move the application to a godaddy web server, ...
    (microsoft.public.dotnet.framework.aspnet)

Loading