topic Websocket not connecting when using alias to Qlik Sense server in Integration, Extension & APIs

Websocket not connecting when using alias to Qlik Sense server

vegard_bakke — Thu, 09 Aug 2018 09:12:11 GMT

And, yes, the alias names are registered in the white list for the virtual proxy.

Using the "native hostname" the web socket is initiated using the http request:

GET ws://qlik-qap01/public/app/0cee61cf-6933-4a40-89cb-690459ef699c?reloadUri=http%3A%2F%2Fqlik-qap01%2Fpublic%2Fextensions%2Fmashup%2Fmashup.html

It returns 101 Switching Protocols, and everything works fine.

Using an alias, however, Qlik is initiating the web socket using the http request:

GET ws://qlik-qap01.local.domain.no/public/app/%3Ftransient%3D?reloadUri=http%3A%2F%2Fqlik-qap01.local.domain.no%2Fpublic%2Fextensions%2Fmashup%2Fmashup.html

This also returns 101 Switching and I receive the same two initial web socket frames from the srever: OnAuthenticationInformation, and OnConnected. But no frames are ever being sent from the browser to the Qlik Sense Server.

The alias name is a straight alias for native hostname, no reverse proxies, or other network routing etc.

We are using Qlik Sense Feb 2018 (12..5.2).

Anyone else experiencing the same? Where does this '%3Ftransiant%3D' come from, and why? Is that the cause, or a symptom?

Any help appreciated!

Cheers,

Vegard

Re: Websocket not connecting when using alias to Qlik Sense server

ErikWetterberg — Fri, 10 Aug 2018 13:32:54 GMT

Hi,

The ''transient' stuff is what the framework uses when it does not have an app ID, like when you're getting the app list. Verify that you really include the app ID in your call.

Erik Wetterberg

http://extendingqlik.upper88.com

Re: Websocket not connecting when using alias to Qlik Sense server

vegard_bakke — Fri, 10 Aug 2018 13:37:54 GMT

Good catch, you might be right. I'll check this out on Tuesday. I've got some automatic appId logic so that everything works on both test and prod server. But as you say, it might be the case for it not working now... Cheers!

Re: Websocket not connecting when using alias to Qlik Sense server

vegard_bakke — Tue, 14 Aug 2018 10:16:47 GMT

You were so right, Erik!

My logic for selecting the right appId, was depending on the server hostname. (TEST-server vs PROD-server.)

Which, I now had all forgotten about. Thank you for reminding me.
Haven't fixed my code yet, but I have confirmed that accessing an early mashup not using this logic works with both native hostname as well as aliases!

Thank you Erik!