Actions
Task #89347
openProvide strong defaults for anchor noreferred/noopener attribute
Status:
New
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
Start date:
2019-10-04
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Sprint Focus:
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¶
noopener
only has an effect of "opened" window contexts (e.g.target="_blank"
)noreferrer
might 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/abc
when 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
Referrer: https://typo3-website.org/user-restricted-internal/product-abc-sucks
pointing tohttps://remote-vendor.com/prodct-abc
- 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-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
Updated by Oliver Hader about 5 years ago
- Related to Feature #78488: Add rel="noopener noreferrer" to links when target is set to _blank added
Updated by Christian Eßl over 4 years ago
- Related to Bug #89757: Fix noopener noreferrer issue added
Updated by Christian Eßl over 4 years ago
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".
Updated by Oliver Hader almost 3 years ago
- Related to Task #96379: [FEATURE] Add rel="noopener noreferrer" to all f:link.external links added
Actions