Release Notes, ShareFile Web Application v19.17

  • 1
  • Announcement
  • Updated 1 year ago
  • (Edited)
We are pleased to announce the release of ShareFile Web Application v19.17, which includes the following changes. These changes will be available to all customers in the coming week.

New changes

Customer issues fixed in 19.17

  • Creating a new Microsoft Office file might fail due to invalid characters in the file name.
  • Users might be able to edit the folder expiration date for Personal Folders.
  • When exporting logs using a cross tenant or cross user, no exception is thrown.
  • Child folders might appear at the same level as their parent folders.
  • A fix has been added to address an issue with the creation of client users in the add user to folder process.
Who needs to know?

ShareFile Web Application updates are intended for all customers. 


You can learn more about ShareFile apps and features at our Support Site (
Photo of Alberto Diaz

Alberto Diaz, Technical Writer

  • 11 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Ross Bender

Ross Bender

  • 86 Posts
  • 17 Reply Likes
The change in Referrer header broke our SAML/SSO integration. We use Netscaler as our IdP and we had our Sharefile policy bound based on requests that originate from Sharefile, as detected in the Referrer header. When the above change was released, the Sharefile site started returning a response header Referrer-Policy: same-origin, which instructs the browser not to attach the Referrer header when passing data to another site (which is the case in SAML SSO).

This was hard to detect, as it appears that not all browsers respect the Referrer-Policy header (looking at you, IE). The Sharefile Drive Mapper tool must be using IE under the hood as it was also not impacted. Chrome, Firefox, and Safari users were affected.

To work around this we updated our IdP profile to include the service provider ID to match the issuer of the incoming SAML request ( More detail at We also had to bind our policy with a "gotoPriorityExpression" of "NEXT" (previously set to "END").

Hopefully this can help someone else.