Repository navigation
Verify installed-plugin coexistence through real WordPress HTTP requests - #131
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When WebDecoy is installed alongside redirect and security plugins, the earlier hook fixture alone could not establish whether login, redirects and detection still worked through a full WordPress request. This adds a disposable installed-plugin HTTP matrix and records the measured results: no conflict observed in the tested flows with Redirection, WPS Hide Login and Wordfence.
The 122-case primary matrix uses full WordPress 7.1.4, PHP 8.3.33, MariaDB 11.8.9 and official pinned plugin packages. It covers each companion separately, the combined stack in different load orders, Wordfence enforcement and native
auto_prepend_file. Each request matches an independent server receipt; detections and AI-counter increments are checked in real SQL storage. Correct-credential login reaches authenticated admin, redirects preserve detections, and WebDecoy's monitor/block behavior remains functional.The results also document two count boundaries: Wordfence can stop a request before WebDecoy runs, and an already-blocked WebDecoy IP can receive another 403 without a fresh detection row. Neither case demonstrates access to a protected action.
Validation:
Wordfence is unlicensed/offline with no downloaded vendor signatures; its local manual UA rule was exercised. Browser JavaScript/client scanner, licensed feeds, actual CDN/proxy/cache deployments, cloud reporting and Apache/FPM remain outside this specific matrix. The fixture downloads nothing and refuses containers without the test label, read-only root, private network namespace and absent host port mappings.