Server.Execute & HttpHandler

[Sam]

My problem is that when I am trying to use
Server.Execute( "Somehandler.as hx") I am getting HttpException.

[HttpException (0x80004005): Error executing child request for
Somehandler.ash x.]
System.Web.Http ServerUtility.E xecuteInternal( IHttpHandler handler,
TextWriter writer, Boolean preserveForm, Boolean setPreviousPage ,
VirtualPath path, VirtualPath filePath, String physPath, Exception
error, String queryStringOver ride) +3179617
System.Web.Http ServerUtility.E xecute(String path, TextWriter writer,
Boolean preserveForm) +747
System.Web.Http ServerUtility.T ransfer(String path, Boolean preserveForm) +56
System.Web.Http ServerUtility.T ransfer(String path) +26

[Rick Strahl [MVP]]

According to the documentation HttpServerUtilt y.Execute/Transfer only works
with pages... It simply may not work with handlers, because the redirect is
occurring from within the Page Handler framework. If you want to redirect to
a handler you need a physical redirect with Response.Redire ct().

+++ Rick ---

--

Rick Strahl
West Wind Technologies
www.west-wind.com
www.west-wind.com/weblog

"Sam" <fo*@tempuri.or g> wrote in message
news:uQ******** ******@TK2MSFTN GP11.phx.gbl...

My problem is that when I am trying to use
Server.Execute( "Somehandler.as hx") I am getting HttpException.

[HttpException (0x80004005): Error executing child request for
Somehandler.ash x.]
System.Web.Http ServerUtility.E xecuteInternal( IHttpHandler handler,
TextWriter writer, Boolean preserveForm, Boolean setPreviousPage ,
VirtualPath path, VirtualPath filePath, String physPath, Exception error,
String queryStringOver ride) +3179617
System.Web.Http ServerUtility.E xecute(String path, TextWriter writer,
Boolean preserveForm) +747
System.Web.Http ServerUtility.T ransfer(String path, Boolean preserveForm)
+56
System.Web.Http ServerUtility.T ransfer(String path) +26

[Sam]

Rick Strahl [MVP] wrote:

According to the documentation HttpServerUtilt y.Execute/Transfer only works
with pages... It simply may not work with handlers, because the redirect is
occurring from within the Page Handler framework. If you want to redirect to
a handler you need a physical redirect with Response.Redire ct().

+++ Rick ---

I need to save Context.Items and it's impossible to redirect. Anyway my
application need only Server.Execute.

Quote from documentation:

"Executes the handler for the specified virtual path in the context of
the current request."

I trust, there is no reason to prohibit IHttpHanlder derived classes.
See Reflected code of HttpServerUtili ty.ExecuteInter nal:

....
else if (!(handler is Page))
{
error = new HttpException(0 x194, string.Empty);
}
....
handler.Process Request(...) // BUT It's only for Page instances (((
....
object[] objArray2 = new object[] { handler.GetType ().ToString() } ;
throw new
HttpException(S R.GetString("Er ror_executing_c hild_request_fo r_handler",
objArray2), error);
Just remove this first 3 lines of code from assembly.. but I am not MS
employee :)

[Christopher Reed]

I believe that the issue is that .ashx files are handled by the
SimpleHandlerFa ctory while .aspx files are handled by the
PageHandlerFact ory. As Rick indicated in his post, the SimpleHandlerFa ctory
does not the redirect process that occurs with the transfer process because
this is embedded within the Page handler. It's not that the IHttpHandler is
prohibited; it's because the simple handler doesn't understand what a page
is necessarily.

Now, what are you trying to attempt using a simple handler file in place of
a page file?
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Sam" <fo*@tempuri.or g> wrote in message
news:OH******** ******@TK2MSFTN GP11.phx.gbl...

Rick Strahl [MVP] wrote:

According to the documentation HttpServerUtilt y.Execute/Transfer only
works with pages... It simply may not work with handlers, because the
redirect is occurring from within the Page Handler framework. If you want
to redirect to a handler you need a physical redirect with
Response.Redire ct().

+++ Rick ---

I need to save Context.Items and it's impossible to redirect. Anyway my
application need only Server.Execute.

Quote from documentation:

"Executes the handler for the specified virtual path in the context of the
current request."

I trust, there is no reason to prohibit IHttpHanlder derived classes.
See Reflected code of HttpServerUtili ty.ExecuteInter nal:

...
else if (!(handler is Page))
{
error = new HttpException(0 x194, string.Empty);
}
...
handler.Process Request(...) // BUT It's only for Page instances (((
...
object[] objArray2 = new object[] { handler.GetType ().ToString() } ;
throw new
HttpException(S R.GetString("Er ror_executing_c hild_request_fo r_handler",
objArray2), error);
Just remove this first 3 lines of code from assembly.. but I am not MS
employee :)

[Sam]

Christopher Reed wrote:

I believe that the issue is that .ashx files are handled by the
SimpleHandlerFa ctory while .aspx files are handled by the
PageHandlerFact ory. As Rick indicated in his post, the SimpleHandlerFa ctory
does not the redirect process that occurs with the transfer process because
this is embedded within the Page handler. It's not that the IHttpHandler is
prohibited; it's because the simple handler doesn't understand what a page
is necessarily.

Now, what are you trying to attempt using a simple handler file in place of
a page file?

It's not depended on Handler factories or something else. There is not
necessary ashx or aspx or jpg. It's a bug, and this bug must be fixed.
If method signature is: Server.Execute( IHttpHandler handler, ...) why I
have an exception here? Instead it there must be Server.Execute( Page
page,...) if handlers are prohibied. Is MS afraid that someone inherit
ASP.NET :)?

Please vote bugreport:

http://lab.msdn.microsoft.com/produc...a-e0dc82b43356

[Sam]

Rick Strahl [MVP] wrote:

According to the documentation HttpServerUtilt y.Execute/Transfer only works
with pages... It simply may not work with handlers, because the redirect is
occurring from within the Page Handler framework. If you want to redirect to
a handler you need a physical redirect with Response.Redire ct().

+++ Rick ---

I need to save Context.Items and it's impossible to direct redirect.
Anyway my
application need only Server.Execute.

Quote from documentation:

"Executes the handler for the specified virtual path in the context of
the current request."

I trust, there is no reason to prohibit IHttpHanlder derived classes.
See Reflected code of HttpServerUtili ty.ExecuteInter nal:

....
else if (!(handler is Page))
{
error = new HttpException(0 x194, string.Empty);
}
....
handler.Process Request(...) // BUT It's only for Page instances (((
....
object[] objArray2 = new object[] { handler.GetType ().ToString() } ;
throw new
HttpException(S R.GetString("Er ror_executing_c hild_request_fo r_handler",
objArray2), error);
Just remove this first 3 lines of code from assembly.. but I am not MS
employee :)

Next issue: Why I see the same behaviour with
Server.Execute( IHttphandler handler, ...)? Here is IHttpHandler as
method parameter.. and it don't work anyway. Why not System.Web.Page
instead of IHttpHandler, if handlers are prohibited? True is buried
within 3 lines above.

Quote from docs for HttpServerUtili ty.Execute(IHtt pHandler, TextWriter,
Boolean):
"Executes the current request by using a custom HTTP handler that
implements the IHttpHandler interface. A TextWriter object captures
output from the page and specifies whether to clear the QueryString and
Form collections."

[Sam]

Rick Strahl [MVP] wrote:

According to the documentation HttpServerUtilt y.Execute/Transfer only works
with pages... It simply may not work with handlers, because the redirect is
occurring from within the Page Handler framework. If you want to redirect to
a handler you need a physical redirect with Response.Redire ct().

+++ Rick ---

I need to save Context.Items and it's impossible to direct redirect.

Quote from documentation:

"Executes the handler for the specified virtual path in the context of
the current request."

I trust, there is no reason to prohibit IHttpHanlder derived classes.
See Reflected code of HttpServerUtili ty.ExecuteInter nal:

....
else if (!(handler is Page))
{
error = new HttpException(0 x194, string.Empty);
}
....
handler.Process Request(...) // BUT It's only for Page instances (((
....
object[] objArray2 = new object[] { handler.GetType ().ToString() } ;
throw new
HttpException(S R.GetString("Er ror_executing_c hild_request_fo r_handler",
objArray2), error);
Just remove this first 3 lines of code from assembly.. but I am not MS
employee :)

Next issue: Why I see the same behaviour with
Server.Execute( IHttphandler handler, ...)? Here is IHttpHandler as
method parameter.. and it don't work anyway. Why not System.Web.Page
instead of IHttpHandler, if handlers are prohibited? True is buried
within 3 lines above.

Quote from docs for HttpServerUtili ty.Execute(IHtt pHandler, TextWriter,
Boolean):
"Executes the current request by using a custom HTTP handler that
implements the IHttpHandler interface. A TextWriter object captures
output from the page and specifies whether to clear the QueryString and
Form collections."