3 Replies Latest reply: Aug 14, 2018 6:16 AM by Vegard Bakke RSS

    Websocket not connecting when using alias to Qlik Sense server

    Vegard Bakke

      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!