Issue Bug Closed

#19464Return URL: Double Encoded characters cause server error

Bernie Pfister 10/16/08, 04:19 updated 09/09/13, 10:15

Description

On our RedHat server, double encoded characters in the return url cause a server error 500.

The forward slash character / can be encoded like this: %2F (HEX encode)

But it can also be encoded like this: %252F (Double encode)

The latter is used in TYPO3 return urls, but causes the above server error. It works when using the HEX encoded characters.

URL like this doesn’t work:
…&returnUrl=http%3A%2F%2F … file_list.php?id=%252Fvar%252Fwww%252F…

This URL works:
…&returnUrl=http%3A%2F%2F … file_list.php?id=%2Fvar%2Fwww%2F…

From what I was reading, there are security issues with this encoding method, which might be the reason that it’s disabled on some servers.

(issue imported from #M9572)

Reviews 0

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