anubis/lib/testdata
Xe Iaso 4ead3ed16e
fix(config): deprecate the report_as field for challenges (#1311)
* fix(config): deprecate the report_as field for challenges

This was a bad idea when it was added and it is irresponsible to
continue to have it. It causes more UX problems than it fixes with
slight of hand.

Closes: #1310
Closes: #1307
Signed-off-by: Xe Iaso <me@xeiaso.net>

* fix(policy): use the new logger for config validation messages

Signed-off-by: Xe Iaso <me@xeiaso.net>

* docs(admin/thresholds): remove this report_as setting

Signed-off-by: Xe Iaso <me@xeiaso.net>

---------

Signed-off-by: Xe Iaso <me@xeiaso.net>
2025-11-25 23:25:17 -05:00
..
aggressive_403.yaml feat(config): custom weight thresholds via CEL (#688) 2025-06-18 16:58:31 -04:00
cloudflare-workers-cel.yaml feat(lib): ensure that clients store cookies (#501) 2025-05-16 13:03:40 -04:00
cloudflare-workers-header.yaml feat(lib): ensure that clients store cookies (#501) 2025-05-16 13:03:40 -04:00
hack-test.json feat: implement challenge registry (#607) 2025-06-04 02:01:58 +00:00
hack-test.yaml feat: implement challenge registry (#607) 2025-06-04 02:01:58 +00:00
invalid-challenge-method.yaml fix(config): deprecate the report_as field for challenges (#1311) 2025-11-25 23:25:17 -05:00
permissive.yaml test(lib): add a test for the X-Forwarded-For middleware (#912) 2025-07-25 10:58:41 -04:00
rule_change.yaml feat(lib): annotate cookies with what rule was passed (#576) 2025-05-30 14:42:02 -04:00
test_config.yaml fix(config): deprecate the report_as field for challenges (#1311) 2025-11-25 23:25:17 -05:00
test_config_no_thresholds.yaml fix(web): embed challenge ID in pass-challenge invocations (#944) 2025-08-04 18:49:19 +00:00
zero_difficulty.yaml fix(config): deprecate the report_as field for challenges (#1311) 2025-11-25 23:25:17 -05:00