Last Modified: Jun 10, 2021
See more info
Known Affected Versions:
14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.2, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.1.3, 188.8.131.52, 14.1.4, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.0.0, 15.0.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Dec 17, 2018
Some fields in the Bot Defense request log have been supplanted by new ones that add more information reflecting new features. There are duplicated fields for Bot Defense request log. The previous fields are being kept for backward compatibility so that existing code reading the remote logs do not break. Their presence might introduce confusion as to their significance and use.
Redundant fields that may create confusion.
Using the Bot Defense remote logger.
You can safely ignore these fields and use the new ones.
The following fields in the Bot Defense request remote log are deprecated, and their new replacement fields should be used instead: -- 'classification_reason': Currently always empty string. The classification is implied by the detected signatures and/or anomalies. -- 'request_status': Replaced by 'new_request_status' in conjunction with 'class' and 'actual_verification_action'. -- 'reason': Currently always empty string. The reason is now conveyed by: 'configured_mitigation_action_reason', 'actual_mitigation_action_reason' and 'browser_actual_verification_action_reason' -- 'action': Replaced by 'actual_verification_action' and 'actual_mitigation_action'. -- 'previous_action': Replaced by 'previous_initiated_action' and 'previous_initiated_action_status'. -- 'client_type': Replaced by 'class'. -- 'mobile_is_app': Replaced by 'class'.