No Code Attached Yet J3 Issue bug
avatar johnrix
johnrix
8 Sep 2018

Steps to reproduce the issue

  1. Create a component router that creates/handles URLs with segments containing + symbols (eg. an email with a user alias element such as in https://mysite.org/menuitemalias/user+alias@example.com/)
  2. Attempt to open such a URL and log the content of the segments supplied to the component router

Expected result

Given the above URL, the first segment supplied the the parse() method of the component router should be the email address as given. (To my understanding, + symbols only have special meaning within the query component of a URL, but should be treated literally within the URL path (ref discussion here: https://stackoverflow.com/questions/1005676/urls-and-plus-signs).

Actual result

The + symbol in the URL is translated to a space character before being passed to the component router.

System information (as much as possible)

Joomla 3.8.10, Ubuntu 14.04, Apache 2.4.29

Additional comments

I've tracked this back to the use of urldecode() in libraries/src/Router/SiteRouter.php (line 89). Replacing this with rawurldecode() addresses the problem (though I have not done extensive testing to understand what other implications this change may have).

avatar johnrix johnrix - open - 8 Sep 2018
avatar joomla-cms-bot joomla-cms-bot - labeled - 8 Sep 2018
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 9 Sep 2018

can you please update to latest Version (you are on 3.8.10) and retest?

There are also some similar Issues + Pull Requests open - can you please look if they are about same Topic?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22096.

avatar franz-wohlkoenig franz-wohlkoenig - change - 9 Sep 2018
Status New Information Required
avatar franz-wohlkoenig franz-wohlkoenig - change - 9 Sep 2018
Category com_mailto
avatar brianteeman brianteeman - change - 9 Sep 2018
Labels Added: J3 Issue
avatar brianteeman brianteeman - labeled - 9 Sep 2018
avatar johnrix
johnrix - comment - 10 Sep 2018

Thanks Franz... had not actually realised there were updates - seems there was a DB schema fix waiting for me to push through before I was alerted to the updates. Have done that now and updated to 3.8.12. Problem is as before.

I spent a few minutes searching through the current PRs and issues but have not yet spotted the same issue there.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22096.

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 10 Sep 2018

@johnrix thanks for Comment and make sure its a unique Issue.

avatar franz-wohlkoenig franz-wohlkoenig - change - 10 Sep 2018
Status Information Required Discussion
Build 3.8.10 3.8.12
avatar csthomas
csthomas - comment - 10 Sep 2018

Take a look at #19196 and #19130

avatar johnrix
johnrix - comment - 10 Sep 2018

Interesting... it does include reference to this problem alright. The PR there would not resolve this fully though as far as I can tell from perusing the changes.

avatar jwaisner jwaisner - change - 18 Mar 2020
Status Discussion Information Required
Build master staging
avatar jwaisner
jwaisner - comment - 18 Mar 2020

@johnrix are you still experiencing this in 3.9.16 or the latest staging branch for 3.9?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22096.

avatar johnrix
johnrix - comment - 23 Mar 2020

Hi @jwaisner, I haven't actively tested this, but the line of code in question has not changed in 3.9.16, so I think the answer would be yes.

avatar johnrix
johnrix - comment - 23 Mar 2020

Was able to confirm with a test there now also that it is still behaving the same way.

avatar jwaisner jwaisner - change - 24 Mar 2020
Status Information Required Confirmed
avatar Hackwar Hackwar - change - 18 Feb 2023
Labels Added: No Code Attached Yet bug
Removed: ?
avatar Hackwar Hackwar - labeled - 18 Feb 2023
avatar richard67 richard67 - change - 22 Feb 2023
Status Confirmed Closed
Closed_Date 0000-00-00 00:00:00 2023-02-22 22:22:21
Closed_By richard67
avatar richard67 richard67 - close - 22 Feb 2023
avatar richard67
richard67 - comment - 22 Feb 2023

Closing as having a pull request. Please test #39917 . Thanks in advance.

Add a Comment

Login with GitHub to post a comment