The enabled attribute of the RequestLog tag specifies whether the error logging mode is enabled for the ICAP and HTTP protocols:Įnabled="true" - the logging mode is active.Įnabled="false" - the logging mode is inactive. This log stores errors which may occur when ICAP client and server communicate, and are related to incorrect data formats sent by the ICAP client, misuse of the ICAP protocol, etc. The RequestLog tag is nested within the lcap tag and defines the error logging mode settings for ICAP and HTTP query protocols processed by the ICAP server. You should only enable this mode in rare cases when you are absolutely sure about what your are doing, because it may result in unpredictable failures in the operation of the ICAP client providing traffic.
If the mode is active, the 204 response code is sent in return to errors even if it is prohibited by Allow204. If the AlwaysOk tag is omitted, this mode is assumed to be disabled by default. The enabled attribute of the AlwaysOk tag specifies whether the "always ok" mode is active: In this mode, the ICAP server responds with code 204 "No modifications" to any errors detected in the ICAP protocol on the client side. The AlwaysOk tag is nested within the Icap tag and enables the "always ok" mode. HTTP commands longer than 7 characters were previously not processed now this length is increased to 32 characters. The string collection buffer size was increased to 32K (it was 8K according to the standard, but the size of individual strings was sometimes over 9.5K). The packets the processing of which resulted in the FROZEN state of the service are saved to a PCAP file in the \log\pcaps directory.Īn error was fixed in the MRA(MRIM) protocol parser which resulted in the EtherSensor EtherCAP service freezing. The service is in the FROZEN state when it has stopped traffic interception due to internal errors or an attack. The "FROZEN" state of the EtherSensor EtherCAP service can now be detected and rectified. The new protocol version was released, supported by new clients. Recognition validity was improved for the MRA (MRIM) protocol. Data sources and objects capture EtherSensor EtherCAP service: