Enhancements and Resolved Issues in Fireware 12.1.3
Release Notes 7
Proxies and Services
lThis release reduces load on the Firebox processor caused by excessive proxy log messages.[FBX-
lThe HTTP proxy no longer fails to get the MD5 hash during a file upload when the file exceeds the
Gateway AV scan limit.[FBX-11577]
lThis release improves IPS and Application Control scanning when Content inspection is enabled on
T15, T30 and XTM330 platforms.[FBX-11354]
lIMAP proxy connection count is now correctly reported in Proxy Connection Statistics for connections
handled by the TCP-UDP proxy. [FBX-10586]
lThis release resolves an issue that caused some websites to fail to load in the Chrome browser for
connections through the HTTPS proxy with TCP MTU probing enabled. [FBX-11280]
lA FireCluster member without a DNSWatch license will now correctly register to the DNSWatch
service when it becomes Master. [FBX-10180]
lThis release resolves an issue that prevented HostWatch from correctly displaying data related to SIP
and H323 proxies. [FBX-10238]
lThis release includes several improvements in Proxy memory usage. [FBX-11465, FBX-9256, FBX-
lThis release resolves a memory leak that occurred when the IMAP proxy was enabled. [FBX-11255]
lThis release resolves an issue that prevented mail from downloading through the IMAP proxy with log
messages that included: “fail to parse fetch argument list”. [FBX-10782]
lThe status of Content Inspection is now included in IMAP proxy log messages when viewed from the
Fireware Web UI.[FBX-10822]
lLog messages generated by the IMAP Proxy now include the TLS Profile name configured in the proxy.
lGateway Wireless Controller updates of AP420 and AP325 no longer fail because of an AP reboot during
the upgrade process. [FBX-11081]
lThis release resolves an issue that caused the Firebox T35-W model to crash when wireless is enabled.
Terms of Use | Privacy Policy | DMCA Policy
2006-2021 Rsmanuals.com