Bug #20519: IDN Domain names handled incorrectly in parts of the backend - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #20519

closed

IDN Domain names handled incorrectly in parts of the backend

Added by Jochen Weiland almost 15 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Steffen Gebert

Category:

Backend User Interface

Target version:

4.5.4

Start date:

2011-05-12

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

TYPO3 Version:

4.2

PHP Version:

5.2

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

If using an IDN (international domain name) like müller.de, the loading of the right frame fails under certain conditions. This is because the domain name is encoded incorrectly.
If you are working with an IDN in the BE and (for example) hide/unhide a page using the context menu (right click) in the page tree, the right frame will not be loaded because of an invalid domain name. Another way to reproduce this is by editing page properties from context menu of the page tree (when closing the right frame).
In older browsers you could bypass this by simply using the punycode version of the domain name (i.e. xn--mller-kva.de instead of müller.de). But now browser will convert the punycode back to IDN.

(issue imported from #M11208)

Files

Download all files

11208.diff (8.08 KB) 11208.diff		Administrator Admin, 2009-06-05 16:55
11208_v2.diff (8.08 KB) 11208_v2.diff		Administrator Admin, 2009-07-14 12:15
11208_v3.diff (9.64 KB) 11208_v3.diff		Administrator Admin, 2011-01-31 23:13
20519_was_11208_v4.diff (9.66 KB) 20519_was_11208_v4.diff		Joh. Feustel, 2011-06-05 12:56

Subtasks 1 (0 open — 1 closed)

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Joh. Feustel almost 15 years ago

The Problem is that the js code of the context menu adds the complete location including the hostname urlencoded to the returnUrl parameters. Which leads to problems when trying to redirect to the domain with the urlencoded umlauts.
The solution is simply to add only the path and parameter parts of the URI. The host will automatically be added in the correct way by t3lib_div::locationHeaderUrl().

Are there other places besides the context menu and the context menu in filelist module (page properties,paste,delete,hide,unhide etc.) where the redirect error occurs?

I found no other problems in 4.2.6 and trunk with punycode domains yet.

Actions

Copy link

Updated by Chris topher almost 13 years ago

Subject changed from IDN Domain names handelt incorrectly in parts of the backend to IDN Domain names handled incorrectly in parts of the backend
Target version deleted (0)

Actions

Copy link

Updated by Joh. Feustel almost 13 years ago

File 20519_was_11208_v4.diff 20519_was_11208_v4.diff added

Actions

Copy link

Updated by Joh. Feustel almost 13 years ago

How to test:
Run TYPO3 on IDN domain like xn--tst-qla.org (täst.org). Note that you need a TLD which supports IDN domains (see https://secure.wikimedia.org/wikipedia/de/wiki/Internationalizing_Domain_Names_in_Applications#Zeichens.C3.A4tze) otherwise the browser will just show up the xn- domain and everything will work because there is no wrong decoding.

Simply add something like

ServerAlias xn--tst-qla.org

to your vhost conf and to /etc/hosts

127.0.0.1 xn--tst-qla.org

Since the pagetree has changed you can test this now by saving an edited or renamed file in the file list module.
Or be clicking on edit in the context menu of a record. Error will occur on saving the record.

Actions

Copy link