Limitations and Precautions for Application Behavior Control

Hardware Requirements

The application behavior control function is supported by all models.

License Requirements

The application behavior control function is not license-controlled.

Component package Requirements

The application behavior control function is dependent on the content security component package. However, it does not require the content security component package be manually loaded. The content security component package is directly placed in the software package and automatically loaded during device startup.

Limitations

• HTTP behavior control supports only HTTP1.0 and HTTP1.1. HTTP2.0 is not supported.
• Upload and download file size control does not apply to files in resumable upload and download.
• The HTTP file download control option is used to control file download through HTTP. If you use a dedicated download tool (such as BT and eMule) on the file download page, the control cannot be implemented on the download tool.
• The application behavior control may function improperly if the forward and return packet paths are different.
• Application behavior control supports the following file types:
  • Executable files: exe, msi, rpm, ocx, a, lib, o, so, elf, out, dll, sys, cmd, bat, and bin;
  • Compressed files: rar, zip, imp, cab, gzip, tar, gz, bz2, tgz, and apk;
  • CD-ROM image file: iso;
  • Office files: doc, docx, xls, xlsx, and ppt;
  • Text files: txt, c, and cpp;
  • Video files: rm, rvmb, wmv, avi, mkv, mov, mp4, mpeg, asf, mpg, vob, and flv;
  • Audio files: mp3, wav, wma, ra, ape, au, ogg, smil, wmf, pict, pub, and dmg.
• Application behavior control supports IPv4 and IPv6.

Precautions

If the FW is deployed between two routers, and the routers detect each other through BFD, you are advised to properly prolong the BFD time (longer than 100 ms is recommended) to prevent BFD flapping resulting from occasional network congestion.