Disable CRC
The Web Transfer Client (WTC) can validate the integrity of files transferred to and from EFT. Cyclical Redundancy Check (CRC32) is enabled on the WTC by default. The EFT administrator must have enabled CRC in its FTP configuration to take advantage of this feature.
With CRC enabled, when the WTC transfers a file to or from EFT, it automatically queries EFT for the CRC value of the file, then compares it to the CRC value for the local file. If they match, the transfer is reported as successful. If they do not match, the system reports a "CRC Failure." The user can then retry the transfer, if necessary. The client does not automatically retry the transfer if they do not match.
If upload verifications are not required, you can disable CRC in the WTC configuration file.
The HTML5 version of the Web Transfer Client does not support a CRC-check for downloaded files because of the limited access of html/js to the client file system. The process of initiating a download is human driven and can NOT be intercepted by a JavaScript API; it is wholly managed by the browser itself, for security reasons. Further, the browser cannot arbitrarily read files on the local file system (for obvious security reasons), so EFT cannot read contents of downloaded files to do CRC32, and thus cannot issue a follow-up HEAD request to verify the integrity of the download.
To disable CRC
-
In C:\Program Files (x86)\Globalscape\EFT Server Enterprise\web\public\EFTClient\jument\scripts, find the adminConfig.js file. (There is a number in front of the name.)
-
Open the configuration file in a text editor, such as Notepad++. (It may be necessary to change the extension from JS to TXT to view it properly.)
-
At the very bottom of the file, find the following text:
gsb.config.crcVerifications = true;
-
Change true to false, then save the file.
-
If you changed the name of the file to edit it, be sure to change it back.
-
Now transfers will be processed without CRC.