Response.End() and CompleteRequest()

c# request response
Raed Alsaleh picture Raed Alsaleh · Mar 28, 2013 · Viewed 19.9k times · Source

What are the advantage and disadvantage for each of Response.End() and CompleteRequest()? Where should I and should I not use them? I looked at this question but I didn't get a proper answer.

Answer

Dai picture Dai · Mar 28, 2013

HttpResponse.End flushes the output buffer to the client and terminates the current request-handling thread (this is bad), whereas HttpApplication.CompleteRequest tells ASP.NET to immediately skip all future stages in the ASP.NET pipeline and jump directly to the EndRequest step (which also raises the HttpApplication.EndRequest event). The request thread then proceeds with normal end-of-life cleanup.

So, Response.End is like an ejector seat: it quickly ends things, but means you lose control and might be unnecessarily harsh. Whereas CompleteRequest is like making an emergency landing at the nearest airport.

Related questions

get current page from url

I want to write a c# method to retrieve the current page. eg Default6.aspx I know I can do the following: string url = HttpContext.Current.Request.Url.AbsoluteUri; // http://localhost:1302/TESTERS/Default6.aspx string path = HttpContext.Current.Request.Url.…

Read More
How to get full host name + port number in Application_Start of Global.aspx?

I tried Uri uri = HttpContext.Current.Request.Url; String host = uri.Scheme + Uri.SchemeDelimiter + uri.Host + ":" + uri.Port; and it worked well on my local machine, but when being published to IIS7, there is an exception saying System.Web.HttpException: …

Read More
How to use HttpClient to send content in body of GET request?

Currently to send a parameterized GET request to an API interface I am writing the following code: api/master/city/filter?cityid=1&citycode='ny' But I see that there is a limit on the URL length of 2,083 characters. To …

Read More