This is a migrated thread and some comments may be shown as answers.

R3 2017 Update has HttpContext?

1 Answer 32 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Justin
Top achievements
Rank 1
Justin asked on 09 Oct 2017, 07:00 PM

On the Release History for R3 2017 (version 11.2.17.913) it has the follwing listed:

FIXED
Services
HttpContext.Current is not availble during the report processing

 

Does this mean that the HttpContext.Current is now available during report processing?  Or is it still not available?

1 Answer, 1 is accepted

Sort by
0
Nasko
Telerik team
answered on 12 Oct 2017, 11:44 AM
Hello Justin,

There was an issue with HttpContext.Current being lost which was introduced in Telerik Reporting R3 2016. The current context was available in the Reporting REST Service methods and in the report's constructor during the GetParameters and CreateInstance calls. However, on CreateDocument the report source was being processed internally and the current context was not available.
This issue is fixed in the R3 2017 release, which means that the HttpContext.Current is now available during report processing.

Regards,
Nasko
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
Tags
General Discussions
Asked by
Justin
Top achievements
Rank 1
Answers by
Nasko
Telerik team
Share this question
or