title: Use of Response.End when forcing PDF Download
body: <p>We had a problem recently where one of the developers had changed a line of code from using <code>HttpResponse.End</code> to using <code>HttpApplication.CompleteRequest</code> when forcing a PDF to download in a similar fashion to the following:
  <a href="https://stackoverflow.com/a/8590579/3856039">https://stackoverflow.com/a/8590579/3856039</a></p>
  
  <p>Doing so caused some PDF's to fail to download due to a non-breaking space issue so the code was changed back to using <code>HttpResponse.End</code>.</p>
  
  <p>However, in helping my colleague I was carrying out some research and I came across the following question:
  <a href="https://stackoverflow.com/q/1087777/3856039">Is Response.End() considered harmful?</a></p>
  
  <p>Which links to:
  <a href="https://blogs.msdn.microsoft.com/aspnetue/2010/05/25/response-end-response-close-and-how-customer-feedback-helps-us-improve-msdn-documentation/" rel="nofollow noreferrer">https://blogs.msdn.microsoft.com/aspnetue/2010/05/25/response-end-response-close-and-how-customer-feedback-helps-us-improve-msdn-documentation/</a></p>
  
  <p>Given what is documented in the MSDN blog post, it sounds like using <code>HttpResponse.End</code> is the wrong approach, so I was wondering if it is even needed or whether there is a better approach?</p>