DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32846>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32846
Summary: multiviews behaviour changed from 1.3 to 2.0 ?
Product: Apache httpd-2.0
Version: 2.0.52
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: mod_negotiation
AssignedTo: bugs@httpd.apache.org
ReportedBy: frans@quanza.net
hi,
I've recently upgraded a box from apache 1.3.24 to 2.0.52.
I'm now getting reports from users that some of their scripts broke
since the install. We're using 'Options MultiViews' in order to be able
to work with clean URL's (URLs that pass arguments to scripts as if
they're directorynames)
I'm using the following PHP script to test (example.php)
<?
$aParams = explode('/', substr($_SERVER["PATH_INFO"],1));
for($i=0;$i<count($aParams);$i++) {
echo "param ".$i." = ".$aParams[$i]."<br />\n";
}
?>
on apache 1.3, when accessing http://server/example/1/2//3 we got the
following output:
param 0 = 1
param 1 = 2
param 2 =
param 3 = 3
However, using the same script on apache 2.0, we got the following
output:
param 0 = 1
param 1 = 2
param 2 = 3
it seems that apache2 is stripping the one slash, however this makes some
production scripts of our client fail, as they do allow for empty
variables.
is there a way to circumvent this behaviour and make apache2 pass the
empty variable to the script as well ? Looking forward to your responses.
Many thanks,
Frans
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
|