TYPO3 Core

This ist actual a feature which turns in a bug in a multi domain installation. So the different domains in the following explainig are important.

• there are two page trees with different domains, eg. domainA.de and domainB.de
• the backend login works with domainA.de
• now you are working in a CE in the page tree of domainB.de and make an external link which jumps to a page of domainA.de (e.g. http://domainA.de/folder/folder/file.html)
• in the html of the RTE the link looks like this: <a href="http://domainA.de/folder/folder/file.html&quot; class="external-link-new-window">my Link</a> Correct so far.
• but after saving the link in the database becomes this: <link folder/folder/file.html" - external-link-new-window "Opens external link in new window">my link</link>

If there would be only one domain or when we work in the page tree of the same domain which we use for the backend login then nothing happens and all would be fine. But we are working in the tree of domainB - and so the link will be rendered wrong to the frontend: <a href="http://domainB.de/folder/folder/file.html&quot;&gt;my link</a> because the missing host is replaced by the host of the frontend domain. But in domainB there is no page with this name - it should be domainA ...

the wrong behavior In short words:

when saving a link in the rte to the database the host is dropped when the host of the link is the same like as the backend login. in the frontend the missing host is replaced with the host of the frontend domain which is often not the domain of the backend login (in a multi domain installation!).

preferred behavior:

the rte should not drop the host in external links when saving the link to the database

(tested on 6.2 in different Installations - host is interpreted as similar only when domain and protocol are the same. The host will not be dropped when the backend runs with https:// and the link begins with http://).