Issue Task Closed

#89347Provide strong defaults for anchor noreferred/noopener attribute

Oliver Hader 10/04/19, 12:02 updated 11/13/26, 14:25

Description

Issue #78488 introduced norefferer & noopener per default for external links, see
https://review.typo3.org/c/Packages/TYPO3.CMS/+/59194

However there are scenarios where this has to be seen in context and scope of the website project:

General

Suggestion

  • make settings configurable
    • TypoScript typolink
    • Site Configuration anchor behavior
  • default settings (when not having TypoScript or Site Configuration loaded – e.g. CLI context) should be strict noopener noreferrer (current scenario)
  • use Referrer-Policy HTTP header as site-wide default instead, use HTML attr to override the default behavior
    • different per site (frontend)
    • common for admin UI (backend)

Side-note

There is a difference between TYPO3 backend and frontend as well. Basically
  • strict default for backend should be noopener noreferrer
  • individual behavior for frontend as outlined in previous sections

Proof-of-Concept

The following example demonstrates a Referrer-Policy (using <meta> instead of an HTTP header here) that is overridden for particular use cases with the referrerpolicy HTML attribute.

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="referrer" content="no-referrer">
    <title>TEST</title>
</head>
<body>
    <ul>
        <li><a href="https://typo3.org">using default policy</a></li>
        <li><a href="https://typo3.org" referrerpolicy="origin">using origin policy</a></li>
        <li><a href="https://typo3.org" referrerpolicy="unsafe-url">using unsafe-url policy</a></li>
        <li><a href="https://typo3.org" referrerpolicy="unsafe-url" rel="noopener">using unsafe-url policy + noopener</a></li>
    </ul>
</body>
</html>

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 9

  1. Christian Eßl commented <span data-processor="relativetime" data-value="2020-07-29T11:28:36+00:00" > 07/29/20, 11:28 </span>

    Currently only noreferrer is used instead of both noreferrer and noopener, because noreferrer alone also implicitly sets noopener as well.
    This is fine with modern browsers, but some older browsers, like IE11 before Windows 10 Creators update, this is not the case and in those instances you would need “noopener” as well to be on the secure side.

    So the configurable solution should also make it possible to set both “noreferrer” and “noopener”.

  2. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-13T14:25:05+00:00" > 11/13/26, 14:25 </span>

    I think we finally fixed this with #107771