| Summary | PATH_INFO problems |
| Queue | DIMP |
| Queue Version | HEAD |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | tedm (at) ipinc (dot) net |
| Created | 01/16/2008 (6400 days ago) |
| Due | |
| Updated | 01/16/2008 (6400 days ago) |
| Assigned | |
| Resolved | 01/16/2008 (6400 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
should strive for factual information, and refrain from making value
judgements. Is the goal of the install documentation to insult
people's choice of software or to assist people in installing dimp?
by default on every 1.3 install I've used.
shown by phpinfo when run under Apache 1.3
In any case, if the directive for turning on PATH_INFO can be skipped
in Apache 2 by a simple code change in dimp, then what is the
objection to making that change?
What part of
"...the restrictions against running it under Apache 1.3
and PHP4/5 SHOULD BE MADE CLEAR IN THE INSTALL DOCUMENTATION..."
are you objecting to?
by default on every 1.3 install I've used.
State ⇒ Not A Bug
PATH_INFO environment variable for all PHP scripts. Every modern
web server supports this"
Incorrect. Apache version 1.3.39 does not support "AcceptPathInfo
On" The docs lead the user to believe it is.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ PATH_INFO problems
Queue ⇒ DIMP
State ⇒ Unconfirmed
PATH_INFO environment variable for all PHP scripts. Every modern
web server supports this"
Incorrect. Apache version 1.3.39 does not support "AcceptPathInfo On"
The docs lead the user to believe it is.
One possible solution if running under PHP5 might be to add
$_SERVER['PATH_INFO'] = (isset($_SERVER['ORIG_PATH_INFO'])) ?
$_SERVER['ORIG_PATH_INFO'] : ' ';
to the beginning of imp.php and dimple.php since they are the only
scripts that support it, and I think PHP5 contains the ORIG_PATH_INFO
variable (but I'm not sure since I don't run PHP5)
PHP4 offers _SERVER["REQUEST_URI"] and _SERVER["PATH_TRANSLATED"] but
that's it. Perhaps a bit of parsing of these?
Horde, IMP, and all the other framework programs run fine on Apache
1.3 and PHP4. It seems pointless to hamstring dimp since it's
unlikely a site that has a running IMP setup is going to mess around
with changing their Apache and PHP configs just to support it.
If there's no interest in the likely trivial amount of coding to
correct this, the restrictions against running it under Apache 1.3 and
PHP4/5 should be made clear in the install documentation