Last Updated: 09 Nov 2022 13:31 by ADMIN
Release R3 2022 SP1
Stephen McDaniel
Created on: 29 Sep 2022 21:39
Type: Bug Report
Better Support for Cookies in WPF Report Viewer

Currently a single instance of the WPF Report Viewer will often use multiple different HttpClient instances to talk to the Report Server.  This means that cookies added as part of earlier requests may not be sent in later requests.  If the Report Server is behind a load balancer that uses cookies to implement 'sticky sessions', this loose behavior with cookies will cause requests to get routed to different servers which is not ideal.  It is possible to use a storage mechanism on the server that natively supports a web farm (such as the Redis storage option) but that can be tricky to set up.  

Instead, if the report viewer were to re-use the same HttpClient instance for all requests (including initial render request, export requests, print requests, etc.), the load balancer could work to route all requests to the same web server and then any storage mechanism (such as the simple File storage option) would work.

This issue was reported back in 2017 and I'm running into the problem again in 2022.  See:

1 comment
Posted on: 06 Oct 2022 12:33

Hello Stephen,

Thank you for this input with the comprehensive description of the scenario and the problem.

We acknowledge the issue as a bug and I have converted the type of the thread to reflect this.

We will try to address the problem with priority.

Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at