paxnu.blogg.se

When Netscaler sees that the cookie ’CtxsUserPreferredClient’ Cookie is missing, it will default to HTML5 Receiver (this is dependent on your Storefront configuration – see further down).

If HTML5 should be used, then we only want to apply the Rerwite policy ”RWP-RES-DISABLE-RECEIVER-CHECK” to suppress the prompt. By using Rewrite Policies we can create these two cookies by ourselves for the user, and therefore suppress the prompt for the user and automatically choose which Receiver Type to use. If Native Receiver has been chosen, then the cookie ’CtxsUserPreferredClient=Native’ will also be created. In a normal scenario, after the Receiver Type has been selected (either automatically or by user), then the cookie ’CtxsClientDetectionDone=true’ will be created in the user’s web browser. This is achieved through Netscaler Rewrite policies.

You can however get rid of below prompt, and at the same also have a mechanism that selects which Receiver Type that should be for a particular user or scenario. See below picture for an example of the prompt I’m referring to. : Citrix, NetScaler By Rasmus Kindberg Translate with Google ⟶Īfter a user has authenticated on a NSGW vServer, the user will either be prompted to select which Receiver Type (HTML5 vs Native) he/she wants to use, or a choice will be made automatically depending on how well the user’s web browser manages to detect a local Citrix Receiver install.