New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trunk: Hexadecimal encoded URLs don't decoded #2631
Comments
Attachment: Example of the user-log with an undecoded URL |
(In [5121]) fixes #2631 |
(In [5122]) fixes #2631 |
The changeset decodes the referer, but the bug report mentions the "link" parameter. Testing with proposed example I still see in the GET request: link=mailto:%69%6e%66%6f@%65%78%61%6d%70%6c%65.%63%6f%6d |
(In [5142]) fixes #2631 |
I think this bug is still fixed since I only removed the unescape() of the referrer, this bug is about the click tracking? |
ah; ok |
Links in a website of the form <a href="mailto:%69%6e%66%6f@%65%78%61%6d%70%6c%65.%63%6f%6d">info@example.com</a> don't get decoded. In the user-log they are shown still encoded.
They should get decoded (normalized) befor they are saved into the database.
The text was updated successfully, but these errors were encountered: