Apply per-path crawler rules from WebDecoy Cloud (#995) - #95
Merged
Merged
Conversation
A connected site now reads its enforcement policy (mode, protected paths, per-path crawler refusals) from the same public config the edge sensor reads, keyed by organization and hostname, and applies it with a PHP port of the shared route resolution that replays all 57 cross-implementation vectors. A crawler of a refused kind on a covered path is refused in Enforce and counted on a watched path or a monitoring site; off-path and excepted requests are untouched. Precedence: cloud rules can only refuse; Block AI crawlers still refuses site-wide; the custom allowlist exempts from the local setting only; the plugin's monitor mode gates every block. Refreshed on the entitlements cron, shown under the AI Crawlers setting, not applied when older than two days.
Merged
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
1 participant
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.
WordPress joins the policy loop (WebDecoy/app#995).
sdk/src/RouteResolution.php: PHP port of the shared route resolution;tests/RouteResolutionTest.phpreplays all 57 vectors frompkg/models/testdata/route_resolution_vectors.json(copied verbatim undertests/vectors/), so Go, the Worker, the Lambda and this plugin cannot disagree.BotDetectortakes acloud_policyoption and, after the local setting, asks the resolution what the covering paths refuse for the crawler's registry behavior. Enforce: refused (crawler_refused, score 100,denied_by: cloud_policy, pattern/behavior/assurance in metadata). Watched path or monitoring site:crawler_would_be_refused, crawler passes.WebDecoy_Cloud_Policy: fetchesin.webdecoy.com/api/v1/clearance/config?aid=<org>&host=<home host>on connect and on the entitlements cron, keeps only the policy fields, refuses to apply a copy older than two days, cleared on disconnect and uninstall. The settings page says what is applied and how fresh it is.assurance: claimed), which refuses nobody who is not making the claim.Not in this PR: the dashboard's outcome ledger still counts edge-reported outcomes only; WordPress refusals arrive as detections carrying the flag and metadata above.
Needs a release after merge (2.9.0).