Skip to content

Test detection ordering around redirects and login requests - #130

Merged
cport1 merged 1 commit into
mainfrom
test/request-hook-order-boundaries
Nov 13, 2026
Merged

cport1 merged 1 commit into
mainfrom
test/request-hook-order-boundaries

Conversation

@cport1

@cport1 cport1 commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

When another plugin redirects and exits before WebDecoy’s init priority1 handler, that request cannot produce a general front-end detection. Later redirects preserve the recorded detection. This PR adds a repeatable 14-case hook-order fixture and documents that observation boundary, including the intentional admin/AJAX exclusions.

The fixture uses the real WordPress hook dispatcher and unmodified plugin constructor, scoring and logging methods, with in-memory WordPress service adapters. Ordinary cases use normal bot scoring; only the reserved-test control uses WebDecoy-Test. It checks both equal-priority registration orders, early bootstrap exits, later page/login redirects and dedicated hook registration. It does not claim full mixed-plugin HTTP or database validation.

Validation: 14/14 focused cases and 229/229 existing tests pass with PHP8.5.10 and WordPress7.1.4 core hook files in a read-only, network-denied sandbox. Reviewed current official Redirection5.10.1, WPS Hide Login1.9.20 and Wordfence9.1.1 sources; full installed-stack certification remains outside this check. No production behavior changes.

@cport1
cport1 merged commit d3c3421 into main Nov 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant