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
0
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
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