WPF ReportViewer cookie behavior

2 posts, 0 answers
  1. Desmond
    Desmond avatar
    1 posts
    Member since:
    Jun 2016

    Posted 19 Dec 2017 Link to this post

    I am trying to use the WPF report viewer with Telerik Reporting REST service deployed on a web farm using FileStorage. Previously, with the WCF service and Silverlight viewer, I was able to deploy on a web farm using cookie-based persistence on our load balancer. After migrating to the WPF viewer, it appears as though the WPF client is not persisting cookies properly between sessions.

    When I first load a report, the viewer registers a new client, the response contains a Set-Cookie header, and then subsequent requests to create instance, create document, get document info, and get document page all include the persistence cookie.

    If I refresh the report, however, the viewer makes a request to get report parameters or create a new instance and does _not_ include the persistence cookie with the request.

    Does the WPF report viewer create a new HttpClient with each request? It should be using a shared singleton instead, as per: https://docs.microsoft.com/en-us/azure/architecture/antipatterns/improper-instantiation/

  2. Todor
    Admin
    Todor avatar
    60 posts

    Posted 22 Dec 2017 Link to this post

    Hello Desmond,

    When you connect a WPF ReportViewer to a Reporting REST Service instance, there will be generated a new ClientId on each request sent by the desktop viewer. This is the current implementation. It is associated with some technical limitations.

    Thank you for the suggestion. We would consider it for our future releases.

    Regards,
    Todor
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top