Product Documentation

To provide HTTP or HTTPS delivery method

Dec 17, 2015

To stream a profile using the HTTP or HTTPS protocol delivery method, use the following example to configure a virtual directory on the Web server.

These steps assume that you already profiled the application and saved it to a file share using a UNC path.

To stream from an HTTPS address, see the additional steps at the end of this procedure. Note that HTTPS requires additional certificate setup. For assistance, contact your network administrator.

The Basic authentication scheme for HTTP is not allowed by default. To allow Basic authentication, create the following registry key:
  • For 32-bit systems: HKEY_LOCAL_MACHINE\Software\Citrix\Rade\AllowUnsecuredHttpAuth
  • For 64-bit systems: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix\Rade\AllowUnsecuredHttpAuth
  • Type: REG_DWORD
  • Value: 1

In the following example, the XenApp server, Web server, and file server are located on the same physical server. This is not a requirement.

To configure the Web server:
  1. Create a file share, if one does not already exist. For example: Web server name: WebServer Physical location on Web server: c:\webProfiles The share name: webProfiles An administrator must share this folder with the “everyone” group assigned READ access and the “administrators” group assigned WRITE access at both the share level and NTFS level. UNC path: \\WebServer\webProfiles
  2. On the Web site hosting the profile, add the following MIME type information:
    • Extension:*
    • MIME type: application/octet-stream
    • Set "Execute Permissions" to NONE

    You can set this information for the Web site hosting the profiles or for a specific folder in the virtual directory that holds the profiles.

  3. In addition, if the profile includes pre-launch or post-exit scripts, also add the following MIME type information for the file extension of each script, such as .bat or .com. Extension: <file extension>, and MIME type: application/octet-stream
  4. In the directory hosting the profiles:
    1. Open Properties and select the Directory tab.
    2. In the Configuration area, keep one application file extension (it doesn't matter which one you keep) and remove all the rest of the file extensions.
    3. Create a placeholder extension for application mapping; for example, ".testcitrix," which should not occur in the profile.
    4. Copy the settings from the file extension that remains (Step 4b) to the placeholder extension.
    5. Delete the file extension that remained in Step 4b, leaving only the placeholder extension from Step 4c.
  5. Create a virtual Web site that points to the file share using the UNC path. For best results, do not use spaces in the URL. For example: HTTP (or HTTPS) path of virtual directory: http://WebServer.domain.com/webProfiles
  6. Turn on Directory Browsing on the virtual Web site. Now you can test the configuration; continuing the example, browse to http://WebServer.domain.com/webProfiles/myApplication/myApplication.profile. If the Web server is configured correctly, the .profile file opens looking like an xml file (not an error message). For HTTP, you have now completed the configuration of the Web server.
  7. For HTTPS, additional binding configuration of the Web server is required. See the additional steps following this procedure, based on your operating system.
  8. In the Citrix AppCenter, publish the application as Streamed to client, Streamed to server, or Streamed if possible, otherwise accessed from a server and continue in the wizard.
  9. On the Location page, enter the full URL path (starting with HTTP or HTTPS) to the profile (browsing to an HTTP location is not supported at this time). Use a fully qualified domain name, not a relative domain name.
  10. Click in the field titled Application to launch from the Citrix streaming application profile to select the application.
  11. Finish the remaining pages of the wizard. The application is ready to stream to the client device using the HTTP delivery method.

To stream from an HTTPS address from Windows Server 2008 additional configuration is required on the Web server. An appropriate Web Server Certificate must be already installed:

  1. From IIS, edit the Bindings for the Web Site.
  2. In the Site Bindings dialog, click Add.
  3. Under Type, choose https.
  4. For SSL certificate, choose the installed Web Server Certificate.
  5. Using the previous example, browse to https://WebServer/webProfiles on the Web server, which must be a member of the domain and have the root certificate installed.

To stream from an HTTPS address from Windows Server 2003, install a Web Server Certificate from a domain certificate authority:

  1. From IIS, open Properties for the virtual Web site.
  2. Click the Directory Security tab.
  3. Under Server Communications, click Server Certificate.
  4. Complete the Web Server Certificate wizard, and using the previous example, browse to https://WebServer/webProfiles on the Web server, which must be a member of the domain and have the root certificate installed.