[#16698] - [4.0-dev] AppVeyor errors | Could not parse the requested URI
- Closed
- 29 Jun 2017
- Medium
- Build: staging
- # 16698
Steps to reproduce the issue
Could not parse the requested URI http://mydomain.comC:\projects\joomla-cms\libraries\vendor\bin\/../phpunit/phpunit/phpunit
https://ci.appveyor.com/project/joomla/joomla-cms/build/1.0.6525/job/le66379sbg5bhgc1
Expected result
tests passes
Actual result
tests fails
System information (as much as possible)
none
Additional comments
none
| Labels |
Added:
?
|
||
| Category | ⇒ | Router / SEF |
| Status | New | ⇒ | Discussion |
To expand on this a bit:
Part of it stems back to this joomla-framework/uri#6 which basically means that we throw an exception if we can't parse the URI (which we didn't before). So honestly we are probably trying to parse this same URL in 3.x but are just ignoring things when we fail to parse that URL
Quite why the URL has a filesystem path in it though to start with I have absolutely no idea :)
mbabker
- | Labels |
Added:
?
|
||
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-06-29 04:33:45 |
| Closed_By | ⇒ | franz-wohlkoenig |
| Closed_Date | 2017-06-29 04:33:45 | ⇒ | 2017-06-29 04:33:46 |
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/16698
closed as having PR #16905
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/16698.
Anybody got any good ideas here. I don't understand how the hell we end up with that URL given none of JURI has changed from 3.x :/