Differences between Response.End() and Response.Flush()

I have code like this:

context.HttpContext.Response.Clear();
context.HttpContext.Response.Write(htmlString);              
context.HttpContext.Response.End();

But when pages are loaded I have an unclosed HTML tag in them. When I replace Response.End() with Response.Flush() it works fine.

What is difference between Response.End() and Response.Flush()?

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

Response.Flush

Forces all currently buffered output to be sent to the client. The
Flush method can be called multiple times during request processing.

Response.End

Sends all currently buffered output to the client, stops execution of
the page, and raises the EndRequest event.

You should try using this code if you are not doing any processing on the page after Response.Write and want to stop processing the page.

    context.HttpContext.Response.Clear();
    context.HttpContext.Response.Write(htmlString);              
    context.HttpContext.Response.Flush(); // send all buffered output to client 
    context.HttpContext.Response.End(); // response.end would work fine now.

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0