Customer is unable to update NetScaler AppFw Signatures from the GUI and receives an error "File too large" when attempting the WAF signature update.

1. Manually download the corresponding “Signatures” file matching your NetScaler build and schema, by using the Mapping File (https://s3.amazonaws.com/NSAppFwSignatures/SignaturesMapping.xml ) in order to obtain the file name and path:
2. Navigate to https://s3.amazonaws.com/NSAppFwSignatures/sigs/[sig xml filename], for example https://s3.amazonaws.com/NSAppFwSignatures/sigs/sig-r12.0b0v102s6.xml
3. Make any signature action changes required on the downloaded XML file.
4. Copy the downloaded files under /var/tmp/ on your NetScaler
5. Run the following command in order to import that new signature file:

   import appfw signatures local:sig-r12.0b0v102s6.xml [name of signature] -autoEnableNewSignatures OF

6. After import of signature file is complete, run the following command to push the object to packet engine so that the imported object is applied:

    update appfw signatures "[name of signature]

7. Confirm that signature has been imported by running:

   show appfw signatures

Problem Cause

WAF engineering provided some additional context in the internal bug tracker for the file size error. "GUI uses systemfile commands to push the WAF and Bot signature files while creating and during update. As new signatures will be added periodically the systemfile API limit need to be higher than 2 MB."