HTTPResponse not arriving at client

Question

I have a http handler which is registered and working fine. Now i want to process a request, and send a custom html response which is then shown on the client.

So my function is written as follows:

public void ProcessRequest(HttpContext _context)
{
    HttpResponse response = _context.Response;

    response.Clear();
    var requestedUrl = _context.Request.Url;
    PhantomModuleController pmc = new PhantomModuleController();
    response.BufferOutput = true;
    var snapshot = pmc.DoThings(requestedUrl); //this returns a string
    response.Write(snapshot); //i put it in the response
    response.ContentType = "text/html";
    response.End(); //it should send it to the client now
}

But according to my fiddler, the response never arrives on the client. In fact, the httpresponse is never even sent.

Did i forget somethiing

Is the http handler an event handler or implementation of an interface or child class or what? Which technology MVC, webforms or other? — P.Brian.Mackey, Nov 19 '13 at 16:04
Could be the same as in this question: http://stackoverflow.com/questions/2246991/httpwebrequest-httpresponse-how-to-send-data-in-the-response — Manuel Zelenka, Nov 19 '13 at 16:08
It is an mvc application and the httphandler derives from ihttphandler — Henk Jansen, Nov 19 '13 at 16:11
Does your call of the client arrive at the handler when you set a breakpoint? Have you registered your handler in your `web.config`? — Aage, Nov 19 '13 at 16:21

score 1 · Answer 1 · answered Nov 19 '13 at 16:27

Because the request is not showing up in Fiddler as being sent back to the client (nor an error back to the client), the routing engine may be getting in the way of the request. The scenerio is described by phil hack.

However, there are other cases where you might have requests for files that don’t exist on disk. For example, if you register an HTTP Handler directly to a type that implements IHttpHandler. Not to mention requests for favicon.ico that the browser makes automatically. ASP.NET Routing attempts to route these requests to a controller. One solution to this is to add an appropriate ignore route to indicate that routing should ignore these requests. Unfortunately, we can’t do something like this: {*path}.aspx/{*pathinfo}

You need to setup the route engine to ignore the route that has the file extension. E.G.

routes.IgnoreRoute("{*allaspx}", new {allaspx=@".*\.aspx(/.*)?"});
routes.IgnoreRoute("{*favicon}", new {favicon=@"(.*/)?favicon.ico(/.*)?"});

HTTPResponse not arriving at client

1 Answers1