| Summary | Horde::selfUrl does not consider webroot |
| Queue | Horde Framework Packages |
| Queue Version | FRAMEWORK_3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | cniemira (at) gmail (dot) com |
| Created | 05/30/2006 (7081 days ago) |
| Due | |
| Updated | 06/29/2006 (7051 days ago) |
| Assigned | 05/30/2006 (7081 days ago) |
| Resolved | 06/29/2006 (7051 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Feedback
registry.php file - and it's not required there, either.
selfUrl() really shouldn't consider the webroot for Horde, either - if
it did, then it would still have to consult PHP_SELF or similar to
find out where it was in the webroot. So I think your best bet is to
fix PHP_SELF.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Horde::selfUrl does not consider webroot
Queue ⇒ Horde Framework Packages
Given the mixed use alongside "Horde::applicationURL," this caues odd
behavior in the rare circumstance where PHP_SELF or SCRIPT_NAME might
be incorrect. In my case, I run horde behind a reverse proxy... and
while the base public URL is "/horde" the base mapped URL is "/".
The issue then manifests as a number of seemingly random broken
links... for example all the menu buttons will work, but if you reach
the "Options" page (services/prefs.php) the target links on it will
not. In my case, they are relative to "/" and not to "/horde."