LLL Referrer Policy Builder / リファラーポリシー作成

What does the comparison show? For each of the eight policy values in the Referrer Policy standard, it shows what a browser puts in the Referer header: the full URL without fragment, the origin only, or nothing, for same-origin requests, cross-origin HTTPS to HTTPS requests, and HTTPS to HTTP downgrades.

What is the default? With no header, browsers apply strict-origin-when-cross-origin (standard revision of November 2020; older browsers used no-referrer-when-downgrade).

How are several values read? The header may list values separated by commas. Unrecognised values are ignored and the last recognised value wins, so an older value can precede a newer one as a fallback. Names must be written exactly as in the standard.

What is not covered? The tool does not apply headers, fetch pages, or simulate browsers. The referrerpolicy attribute, rel="noreferrer", meta tags and browser privacy settings can narrow what is sent. Very long URLs (over 4,096 characters) are reduced to the origin by browsers.

See the Referrer Policy standard and MDN Referrer-Policy.

Requires an EmDash administrator with plugins:manage. The manifest requests no capabilities or network hosts. Inputs are processed in the sandbox without saving or external transmission. Paste only the Referrer-Policy value. Report security issues to contact@lx3.cafe.

0.1.0

• Compare Referrer-Policy values by sent Referer context and copy the header.

Install LLL Referrer Policy Builder in EmDash 1.4 and open it as an administrator. Choose a policy, optionally paste your current Referrer-Policy value, and select Preview. Copy the displayed header into your server, CDN or framework configuration. Check the live response separately.