Skip to content

Verify installed-plugin coexistence through real WordPress HTTP requests - #131

Merged
cport1 merged 1 commit into
mainfrom
test/installed-plugin-stack-compat
Nov 14, 2026
Merged

cport1 merged 1 commit into
mainfrom
test/installed-plugin-stack-compat

Conversation

@cport1

@cport1 cport1 commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

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:

  • 122 primary HTTP cases and 122 independent receipt/status matches passed across 10 scenarios.
  • All 28 native-prepend cases proved the prepend ran; manual Wordfence denies occurred before WordPress loaded.
  • The saved portable runner passed another 28-case extended-mode replay; Compose configuration validation passed.
  • No production plugin code changed. Test fixtures/docs are excluded by the existing release build. Both disposable containers and their tmpfs data were removed.

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.

@cport1
cport1 merged commit f3dee42 into main Nov 14, 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