user34537
user34537

Reputation:

Alternative to Response.End()?

I handle a request begin_request. At the moment i use Response.End() to stop asp.net from doing whatever else. Response.End() throws an exception is there a non exception way i can end the request?

If your wondering why i have no file its bc i tell nginx what file to serve via http response header thus i have nothing else to do in asp.net. Response.End throws an exception which has to collect stack info and all of that. I obviously dont need that and from my past questions i know throwing exceptions are expensive. So how what can i do where?

Upvotes: 10

Views: 24119

Answers (2)

Cᴏʀʏ
Cᴏʀʏ

Reputation: 107526

HttpResponse.End() throws an exception by design; it has to to work.

Only when the ThreadAbortException is thrown, does the thread that's rendering the response end. If there's no exception, the response doesn't end.

One alternative would be to call HttpContext.Current.ApplicationInstance.CompleteRequest instead. This will prevent further code from executing by jumping straight to the Application_EndRequest event.

Upvotes: 17

Royi Namir
Royi Namir

Reputation: 148524

call the HttpContext.Current.ApplicationInstance.CompleteRequest() method instead of Response.End to bypass the code execution to the Application_EndRequest event

http://support.microsoft.com/kb/312629

Upvotes: 12

Related Questions