Re: Http-handlers

From: Joseph Geretz (jgeretz@nospam.com)
Date: 03/16/03 

From: "Joseph Geretz" <jgeretz@nospam.com>
Date: Sat, 15 Mar 2003 20:27:30 -0500

> I found another way of possible do this, but it's partly uggly, but it
> could be conisdered, namely, create an HttpHandler that parses the
> incomming url, find out what is requestet, remap to an .asp page, and
> use an HttpRequest object to get this page on the server locally (will
> generate an extra httprequest on the server though), then this content
> could be sent to the client via response.write or something..
> Possible this would kill the server performance?

I was in this situation myself, briefly. I had my application controller
(i.e. filter) originally engineered as an HttpHandler. This was fine for
instantiating business objects which were engineered as classes
implementing a known interface. It became a barrier though to native WebForm
development, since the HttpHandler becomes the target of the request which
makes it difficult to involve the WebForm itself, (or any aspx script) in
the request. I originally solved the problem exactly as you suggest;
However, depending on the complexity of your aplication, don't underestimate
the amount of code which will be necessary to send query parameters (one
way), form fields (one way) and cookies (bi-directional). In essense, you'll
be rewriting your own web server, which is the position I found myself in.
(Of course, this was really the wrong solution for my problem. An Httpodule,
rather than an HttpHandler is more appropriate for an application filter
since it dos not interfere with the target request. This is ultimately the
solution which I implemented.)

This whole topic makes me wonder why MS couldn't (or wouldn't) provide
backward compatibility to allow the .NET ASPX ISAPI to process both ASP
scripts as well as ASPX scripts.

Relevant Pages

  • Re: Double click
    ... I have a form that folks use to report ... >> written with asp, and it submits to an asp page, and the results are ... > the user clicks the submit button a second time, before the first request ... > been received by the server. ...
    (microsoft.public.inetserver.asp.db)
  • Re: Http-handlers
    ... >Is it an HttpHandler, or an HttpModule? ... HttpHandler block in the machine.config that has the ... HttpForbiddenHandler to prevent serving of .asp pages. ... a request handler which either be ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Double click
    ... > Thanks for your NOT SO FRIENDLY response. ... > written with asp, and it submits to an asp page, and the results are ... been delivered to the user's browser, but after the first request has been ... Unfortunately there isn't a bunch you can do about this on the server side. ...
    (microsoft.public.inetserver.asp.db)
  • Re: .NET.. is it the IIS server ?
    ... start without debugging does not work. ... "Server Application Unavailable ... browser to retry your request. ... > Secure pages with ASP! ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: .NET.. is it the IIS server ?
    ... Secure pages with ASP! ... > start without debugging does not work. ... > "Server Application Unavailable ... > browser to retry your request. ...
    (microsoft.public.dotnet.framework.aspnet.security)