HTML 5 report viewer does not work with SSL / HTTPS

[Fridli Jacober]

Hello together

Today I noticed that the HTML 5 report viewer does not work over SSL / HTTPS because the Kendo UI resources are referenced through normal HTTP protocol.
I found the solution through the Kendo UI forums (replace http://cdn.kendostatic.com with https://kendo.cdn.telerik.com) so either this is an error in the reporting template or I am using an older version of it.

Unfortunately, I'm unable to respond to a topic in the Kendo UI forums section which led me to the solution (http://www.telerik.com/forums/problem-with-cdn-s-security-certificate). The posted link to the "JavaScript dependencies help topic" is not correct anymore or does not lead to the solution itself which I found under "Use the Kendo UI CDN service" in the docs).

Regards

[Stef]

Hello Fridli,

Please test one of the following

1. Download Telerik Kendo UI files locally and update the links to them in the project;
2. Use Telerik Kendo UI CDN over HTTPS - Use the Kendo UI CDN service. 
3. If files are not delivered, check with Fiddler what is the actual error on displaying the page with the viewer. Details about requests and responses can be found in Fiddler - Inspectors - Request/Response - Raw tabs.

If you need further help, post details from Fiddler what happens on loading the page with the viewer.

Regards,
Stef
Telerik

[Fridli Jacober]

Hello Stef

As i wrote the Kendo UI resources were referenced ​to http://cdn.kendostatic.com instead of https://kendo.cdn.telerik.com and through normal HTTP protocol in the Visual Studio report viewer template.
So either my VS report viewer template was outdated or it's an error in the template. This resolution I found in the Kendo UI forums.

Regards

[Stef]

Hello Fridli,

Apologies for the misunderstanding and I am glad to hear that you actually found a solution.

In general, the VS item template for adding an HTML5 Viewer uses links to CDNs for jQuery, FontAwesome and Telerik Kendo UI files in order to avoid downloading them locally, which is caused by the fact there are various Web project templates which may or may not include these files already.

The aim is to produce a page with the Viewer which can work as standalone page. Then depending on the project template and settings, including hosting settings, you can manually edit links to point to local resources or other CDNs.

Regards,
Stef
Telerik