My site is deployed to IIS and is hosting the HTML5 ReportViewer. When accessing the ServiceURL over HTTP everything is working. When access the ServiceURL over HTTPS I'm getting an error "CANNOT POST /myreports/api/reports/clients".
Am I missing a step here ?
BTW - My site is a NodeJS site, hosted on IISNode, with an Angular front-end.
Thanks,
Ciaran
1 Answer, 1 is accepted
0
Hello Ciaran,
You will need to use Telerik Kendo UI CDN links over HTTPS (Use the Kendo UI CDN service) or download them locally and link them from the project folders. The same applies to any links to external resources e.g. FontAwesome and jQuery, including the Reporting REST service.
Note that if the viewers and the service use different domains, you may need to enable CORS to allow the communication between them. Also check the relative paths to CSS, JS and HTML files and how they are resolved on running the page. Path references in the described steps should be adapted according to your project setup. For more information please refer to the MSDN article ASP.NET Web Project Paths.
The recommended troubleshooting approach is to use Fiddler or other proxy tool to check the requests, their responses and statuses. Information about requests and responses content can be seen in Fiddler - Inspectors - Request/Response - Raw tabs.
I hope this information is helpful.
Regards,
Stef
Telerik
You will need to use Telerik Kendo UI CDN links over HTTPS (Use the Kendo UI CDN service) or download them locally and link them from the project folders. The same applies to any links to external resources e.g. FontAwesome and jQuery, including the Reporting REST service.
Note that if the viewers and the service use different domains, you may need to enable CORS to allow the communication between them. Also check the relative paths to CSS, JS and HTML files and how they are resolved on running the page. Path references in the described steps should be adapted according to your project setup. For more information please refer to the MSDN article ASP.NET Web Project Paths.
The recommended troubleshooting approach is to use Fiddler or other proxy tool to check the requests, their responses and statuses. Information about requests and responses content can be seen in Fiddler - Inspectors - Request/Response - Raw tabs.
I hope this information is helpful.
Regards,
Stef
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