URL Link Not working from Published Document (QlikView 12.5)

[parevrac]

Several of our QlikView applications include URL Links embedded within straight tables to open related records within their source system.  All those that are http are still working however since moving to QlikView 12.5 any https URL links result in a 'Can't Open This Page' error when activated from a published document on the Access Point. These links work fine from the development software therefore I can confirm that the URL are correct.

Is there a setting somewhere within QlikView 12.5 that needs to be adjusted to enable https URL?  NOTE: we are running all apps via  AJAX  in Microsoft Edge Chromium

[Kamryn]

---

@parevrac wrote:

Several of our QlikView applications include URL Links embedded within straight tables to open related records within their source system.  All those that are http are still working however since moving to QlikView 12.5 any https URL links result in a 'Can't Open This Page' error when activated from a published document on the Access Point. These links work fine from the development software therefore I can confirm that the URL are correct. ePayitonline Login

Is there a setting somewhere within QlikView 12.5 that needs to be adjusted to enable https URL?  NOTE: we are running all apps via  AJAX  in Microsoft Edge Chromium

---

The issue for us was that the default client for users was set to IE plugin and the document was only published to AJAX. This caused the accesspoint link to be blank when trying to open the documents.

[Daniele_Purrone]

Hi @parevrac 
Are you opening the Access Point in HTTP, or https mode?
When you try top open the https URL, are you getting any certificate issue in the browser? 
The "Can't Open This Page" error, does it contain any response code? (like 400, 404, and so on?)
If you use the developer tools, do you see any specific error?

[parevrac]

Thanks Kamryn, AJAX is default plus we do not have IE Plugin 

Regards Paul

[parevrac]

Hi Daniele

The error code is 0

Thanks for the steer regards developer tools - i will have to get our IT Support to look into this as developer tools are blocked to most users

Regards Paul