Citrix Workspace Website

  1. Cintex Workspace
  2. Citrix Workspace For Windows
  3. Citrix Workspace Website
  4. Citrix Workforce
  5. Arthrex Intranet Citrix
downloadWhy can't I download this file?

Mozilla Firefox

There is a possible workaround for Mozilla Firefox browser.

Citrix

Note: This workaround has security implications; consult the security specialist of your organization to consider the following configuration.

Cintex Workspace

  1. Enforce secure communications between Workspace App for HTML5 and applications or desktops (for example, using IPSec).

  2. Use Mozilla Firefox only for Citrix Receiver for HTML5 (not for general website use).

  3. Enforce a secure configuration for Firefox.

  4. Enable the Firefox network.websocket.allowInsecureFromHTTPS option.

If the preceding configuration is consistent with the security policy of your organization, an administrator can enable launching applications or desktop using the following steps:
  1. Open a new tab in the Firefox browser.

  2. Type about:config in the address bar.

  3. Double-click network.websocket.allowInsecureFromHTTPS and set the value to true.

Note: This Firefox option might not be supported in Citrix Receiver for HTML5 future versions.

WARNING! This option on Firefox affects the operation of entire Firefox, not just Citrix Receiver for HTML5.

Important Note

As of version 9, Safari browser allows insecure web socket connections. Internet Explorer never allowed non SSL/TLS web socket connections from HTTPS websites. Chrome used to allow it behind a flag, but after the Chrome 44 update, this is no longer supported. Firefox allows it behind a flag (as explained earlier in this article), but it is not recommended. Going forward, only secure (SSL/TLS) web socket connections can be made from Receiver for HTML5.

Problem Cause

When Workspace App for HTML5 is hosted on a https site (default and recommended), non SSL/TLS websocket connections are prohibited by browsers.
In explaining the technical reason behind this it is important to understand the following two principles:
1. As opposed to existing as a separate process, Citrix Workspace App for HTML5 operates within the frame and process space of the browser itself. As such the browser has the ability to enforce certain security parameters.

2. Additionally, when any Workspace App for Windows makes a connection to a VDA for either a published desktop or app, the underlying connection is made to the VDA and not the Storefront server as any kind of intermediate proxy.


This second point is less obvious in the case of Citrix Workspace App for HTML5 because the published desktop or application displays within the browser frame and “appears” to be connected via the Storefront server. Despite this appearance though, the underlying TCP/UDP connection is still between the client and the VDA. If the Storefront base URL is SSL enabled (where it begins with https as is best practice) and the VDA is not SSL enabled (which it is not by default) the browser in this case will prevent the connection due to what it sees as an underlying inconsistency. The inconsistency is that while the URL shown in the browser frame is prefixed with https, the actual underlying connection is not https even though it is not obvious to the user.
There are two solutions for this.
Solution 1 is to enable SSL on the VDA using the following guide:

https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/secure/tls.html
This will ensure that the connection path is SSL enabled between the internal client and the VDA.

Citrix Workspace For Windows

Solution 2 is to have your connections from the clients first go through a Citrix Gateway. Citrix Gateway will proxy the connections and perform a SSL handshake between the client and the Citrix Gateway. In this scenario there is no inconsistency and connections via HTML5 Receiver will succeed.

Additional Resources

You can now use the Application probing feature to proactively monitor the health of applications enabling you to fix issues before the user actually experiences them. For more information refer to Citrix Documentation - Application probing.
downloadWhy can't I download this file?Cleanmydrive torrent

  • Type about:config in the address bar.

  • Double-click network.websocket.allowInsecureFromHTTPS and set the value to true.

  • Note: This Firefox option might not be supported in Citrix Receiver for HTML5 future versions.

    WARNING! This option on Firefox affects the operation of entire Firefox, not just Citrix Receiver for HTML5.

    Important Note

    As of version 9, Safari browser allows insecure web socket connections. Internet Explorer never allowed non SSL/TLS web socket connections from HTTPS websites. Chrome used to allow it behind a flag, but after the Chrome 44 update, this is no longer supported. Firefox allows it behind a flag (as explained earlier in this article), but it is not recommended. Going forward, only secure (SSL/TLS) web socket connections can be made from Receiver for HTML5.

    Problem Cause

    Citrix Workspace Website

    When Workspace App for HTML5 is hosted on a https site (default and recommended), non SSL/TLS websocket connections are prohibited by browsers.
    In explaining the technical reason behind this it is important to understand the following two principles:
    1. As opposed to existing as a separate process, Citrix Workspace App for HTML5 operates within the frame and process space of the browser itself. As such the browser has the ability to enforce certain security parameters.

    2. Additionally, when any Workspace App for Windows makes a connection to a VDA for either a published desktop or app, the underlying connection is made to the VDA and not the Storefront server as any kind of intermediate proxy.


    This second point is less obvious in the case of Citrix Workspace App for HTML5 because the published desktop or application displays within the browser frame and “appears” to be connected via the Storefront server. Despite this appearance though, the underlying TCP/UDP connection is still between the client and the VDA. If the Storefront base URL is SSL enabled (where it begins with https as is best practice) and the VDA is not SSL enabled (which it is not by default) the browser in this case will prevent the connection due to what it sees as an underlying inconsistency. The inconsistency is that while the URL shown in the browser frame is prefixed with https, the actual underlying connection is not https even though it is not obvious to the user.
    There are two solutions for this.
    Solution 1 is to enable SSL on the VDA using the following guide:

    https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/secure/tls.html

    Citrix Workforce


    This will ensure that the connection path is SSL enabled between the internal client and the VDA.
    Solution 2 is to have your connections from the clients first go through a Citrix Gateway. Citrix Gateway will proxy the connections and perform a SSL handshake between the client and the Citrix Gateway. In this scenario there is no inconsistency and connections via HTML5 Receiver will succeed.

    Additional Resources

    Arthrex Intranet Citrix

    You can now use the Application probing feature to proactively monitor the health of applications enabling you to fix issues before the user actually experiences them. For more information refer to Citrix Documentation - Application probing.
    Comments are closed.