My Firewall Rule is set to "Legacy CAPTCHA" but the connections caught in the firewall still shows "Managed Challenge'?

[user20752]

Hello, I have a firewall rule set to “Legacy CAPTCHA” and yet when I check my firewall logs, those caught by that rule show up as “Managed Challenge”, why is that? I explicitly set it to “Legacy CAPTCHA” so that those caught in it will be forced to solve one.

[fritex]

Greetings,

Thank you for asking.

I’ve seen “Legacy CAPTCHA” do show up in my Firewall Events two days ago.

I checked again few minutes ago, I do still see it works and appears normally.

Kindly, may I suggest below topic for more related information about the recent change and explanation:

Legacy Captcha showing as action on FW Rules

Greetings, Thank you for asking. It’s a little change in wording according to the stated on the GitHub: From my point of a view, I think it stays as is, I see no need to change it for now. When checked, I can see it’s working as it was: https://developers.cloudflare.com/firewall/cf-firewall-rules/actions [legacy_challenge] Otherwise, kindly and patiently wait for a next reply from someone who might know some additional information to this change.

Legacy Captcha showing as action on FW Rules

As mentioned by @fritex, the action name was simply renamed - there is no change in behavior. However, we strongly recommend the use of Managed Challenge over Legacy CAPTCHA as it provides a significantly better user experience to your users. Further information about Managed Challenge can be found here: https://support.cloudflare.com/hc/en-us/articles/200170136-Understanding-Cloudflare-Captchas-Managed-Challenge-and-Challenge-Passage#managed-challenge.