Why is ASP.NET replacing a Content-Length header with a Transfer-Encoding header when manually flushing a response?

Question

Our web application (ASP.NET Web Forms) has a page that will display a recently generated PDF file to users. Because the PDF file is sometimes quite large, we\'ve implemented a

Answer 1

From an article on MSDN it seems that you can disable chunked encoding:

appcmd set config /section:asp /enableChunkedEncoding:False

But it's mentioned under ASP settings, so it may not apply to a response generated from an ASP.NET handler.