Quantcast
Channel: SQL Server Reporting Services
Viewing all articles
Browse latest Browse all 1418

Adding Bytes to the Reponse Object causes asynchronous report rendering to fail

$
0
0

Okay all I am assuming noone is going to have an answer to this because it is just so 'out-there' but here goes.

I wanted to find a way of making locally processed rdlc files (report definitions) fill the screen in any browser. I managed to do it (woo!) but found the most unbelivably strange thing would happen.

If you set the report viewer to AsyncRendering="true" and then modified the length of the output stream using a response filter which adds characters into the output stream no browser could parse the response. It is generated correctly and the output length is set correctly but the browser does not like it. Even the response header informs the browser of the correct respose size.

If you set AsyncRendering="false"  the browser is okay with it.

Does anyone at all have any idea where I would go to start working out why this would be? For info if you read the actual bytes sent by the server everything is there, no extra characters or blank space. Is there somewhere in the response object other that the outputStream.write that I could be creating the problem?


Viewing all articles
Browse latest Browse all 1418

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>