LLL Redirect Live Page Reconcile

FAQ

What is a collision here? An enabled, literal redirect rule whose source is the same path as a published entry's public path. EmDash 1.4.0 consults redirect rules before it renders a page, so such a page can become unreachable. The Effect column says which side wins under that code, and why some pairs do not collide in practice (for example, a destination that is not a site-relative path, or a path ending in a file extension).

Is this the built-in redirect health check? No. EmDash checks for redirect loops when you create or change a rule. LLL Active Redirects Review looks at chains and rules without recorded hits. This tool compares rule sources with published page paths, which neither does.

Does it predict what visitors get? Not for your site as deployed. The Effect is what the redirect handling in EmDash 1.4.0 does, confirmed by a test against that code. Themes, proxies, CDNs and route caches are outside what this plugin can see.

Why can a rule with a non-ASCII source be missing? Requests carry the percent-encoded path, and the lookup is an exact, case-sensitive string match without decoding. A raw non-ASCII source never matches (tested), so such a rule is not a collision.

Why are pattern rules not listed? They are also checked before pages, but matching them needs a pattern engine. They are counted so you know they exist.

What if there are no rows? No collision among the rules and entries that were read. Limits (1,000 rules, 500 entries) and unresolved URLs produce a partial result.

Where is the report? Plugin KV stores rule sources, destinations, entry IDs, titles and counts, not bodies. One report per user, 24-hour logical expiry, removed on next read or Clear. No CSV or download.

Paid? No. Support/security: contact@lx3.cafe, with redacted examples only.

日本語: 衝突は確認候補です。「結果」はEmDash 1.4.0同梱の処理に対するテストの結果で、実サイトの測定ではありません。

Security

LLL Inc. / MIT / contact@lx3.cafe. Version 0.1.0.

Capabilities: redirects:read, content:read, schema:read. One POST JSON admin route requires plugins:manage and a host caller identity. No public report route, network access, hooks, cron, redirect/content writes or credentials. The plugin cannot create, change or delete a redirect: only the read accessor is granted.

Report metadata (rule sources, destinations, public paths, collection/ID/locale/title, hit counts) can be sensitive. No article body is stored. One report per user, 24-hour logical expiry; the next read or Clear deletes the state; there is no scheduled physical cleanup. Copies in the browser are outside the plugin's control.

Boundaries: 1,000 rules, 500 entries, 100 rules or 20 entries per step, 2048 UTF-8 bytes per URL, 512 KiB of state; partial results on limits or unresolved URLs. URLs with credentials, control characters or non-HTTP schemes are not compared. Output is a plain table, not executable HTML.

Email security issues privately with the version and a redacted reproduction. Do not send tokens, exports or private URLs. No response-time commitment is offered.

Changelog

0.1.0

Initial read-only reconciliation of enabled literal redirect rules against published public paths; manual batches; English/Japanese admin UI; trailing-slash variant, effect classification checked against EmDash 1.4.0; scoped report storage and partial-result warnings. No changes to content or redirects.

Installation

Version 0.1.0. Requires EmDash 1.4.0 or later in the 1.x series and the official sandbox runner (Node/workerd or a supported Cloudflare Worker Loader path). Hosting costs are separate. Use a validated Registry release, check the publisher and signature, confirm that only redirects:read, content:read and schema:read are requested, install as an administrator, then open Redirect Live Pages.

Choose a language, Start, then Continue manually. The plugin reads enabled redirect rules (up to 1,000, 100 per step), then published entries of visible, routable collections (up to 500, 20 per step), and lists each enabled literal rule whose source equals the entry's public path. A rule that differs only by a trailing slash is listed as such, because EmDash 1.4 looks that variant up too.

Each row shows the rule (status, destination, hit count, whether EmDash created it automatically), the entry (collection/ID, locale, title), the public path, the kind of match and an Effect. The Effect states what the redirect handling shipped in EmDash 1.4.0 does when the two meet; it was checked by a test against that code and is not a measurement of your site. Themes, proxies, CDNs and route caches can behave differently.

Not compared, and counted separately: pattern rules, rules containing a query, fragment or placeholder, and pages that are not CMS entries. No row is not an all-clear: read the status and counts. Nothing is edited; fix rules in EmDash's own redirect screen.

Free; no paid edition or key. Contact: contact@lx3.cafe.

日本語: 有効な完全一致のリダイレクト元が、公開中の記事の公開パスと重なるものを手動で一覧にします。「結果」はEmDash 1.4.0同梱の処理に対するテストで確かめた内容で、お使いのサイトの実測ではありません。照合外のルールは件数のみ表示します。