#89347Provide strong defaults for anchor noreferred/noopener attribute
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
noopeneronly has an effect of “opened” window contexts (e.g.target="_blank")noreferrermight contradict tracking & analyzation on websites- e.g. “which site is has similar information” – good use of referrer in a scope similar to “LOD”
Referrer: https://typo3-website.org/resources/car-engines/abcwhen openinghttps://remote-vendor.com/cars/xyz
- e.g. “which site has similar problems” – bad use of referrer, when e.g. sensitive areas point public resources
- e.g. “which site is has similar information” – good use of referrer in a scope similar to “LOD”
Suggestion
- make settings configurable
- TypoScript
typolink - Site Configuration anchor behavior
- TypoScript
- default settings (when not having TypoScript or Site Configuration loaded – e.g. CLI context) should be strict
noopener noreferrer(current scenario) - use
Referrer-PolicyHTTP 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.
Related issues 4
History 9
-
Oliver Hader changed Related to #78488 <span data-processor="relativetime" data-value="2019-10-04T12:02:43+00:00" > 10/04/19, 12:02 </span>
-
Oliver Hader changed description <span data-processor="relativetime" data-value="2019-10-04T12:05:23+00:00" > 10/04/19, 12:05 </span>
-
Christian Eßl changed Related to #89757 <span data-processor="relativetime" data-value="2020-07-29T11:25:35+00:00" > 07/29/20, 11:25 </span>
-
Oliver Hader changed description <span data-processor="relativetime" data-value="2021-12-17T11:47:38+00:00" > 12/17/21, 11:47 </span>
-
Oliver Hader changed Related to #96379 <span data-processor="relativetime" data-value="2021-12-17T11:48:02+00:00" > 12/17/21, 11:48 </span>
-
Oliver Hader changed description <span data-processor="relativetime" data-value="2025-10-14T20:41:06+00:00" > 10/14/25, 20:41 </span>
-
Albrecht Köhnlein changed Related to #107771 <span data-processor="relativetime" data-value="2025-10-17T19:29:01+00:00" > 10/17/25, 19:29 </span>
-
Benni Mack commented and changed status
NewClosed <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
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”.