php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #13925 SCRIPT_NAME in Apache 1.3.22 wrong (or at least different)
Submitted: 2001-11-04 21:56 UTC Modified: 2002-08-14 13:50 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: bobsledbob at yahoo dot com Assigned:
Status: Not a bug Package: Apache related
PHP Version: 4.0.6 OS: FreeBSD 4.4-Stable
Private report: No CVE-ID: None
View Developer Edit
 [2001-11-04 21:56 UTC] bobsledbob at yahoo dot com 
Hi,

I have a website on an ISP that runs FreeBSD 4.4 with a recently upgraded Apache 1.3.22 webserver and PHP 4.06 compiled as CGI.  My sight relies on the $SCRIPT_NAME PHP global variable.  It seems that this variable is getting set differently with the new Apache?  Here's an example:

URL:
  http://some.website.com/script/foo/bar
where
  script = script.php using Apache multiviews

Before (Apache 1.3.20 / PHP 4.06):
$PATH_INFO = /foo/bar
$SCRIPT_NAME = /script

After (Apache 1.3.22 / PHP 4.06):
$PATH_INFO = /foo/bar
$SCRIPT_NAME = /script/foo/bar/script.php

I'm sorry I won't be able to give too much detail of this bug because I don't have too much access to the machine (on the ISP), but let me know how I can help with this issue and I'd be glad to do what I can.

Thanks.

Adam Taft
bobsledbob@yahoo.com

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-11-13 17:50 UTC] bate@php.net 
Checked with latest CVS
and PHP 4.1.0RC1 + RC2

Script Output:
$PATH_INFO = /foo/bar
$SCRIPT_NAME = /script/foo/bar/script.php

I checked that too under RedHat + SuSE 7.x
with PHP 4.0.6
$PATH_INFO = /foo/bar
$SCRIPT_NAME = /script/foo/bar/script.php
 [2001-12-12 15:44 UTC] derick@php.net 
I think this is related to the apache bug at:

http://bugs.apache.org/index.cgi/full/8582
 [2002-08-14 13:50 UTC] iliaa@php.net 
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem does not imply a bug in PHP itself.
For a list of more appropriate places to ask for help using PHP,
please visit http://www.php.net/support.php

Thank you for your interest in PHP.

This bug was indeed the result of a bug in Apache. In Apache version later then 1.3.22 this behavior is correct once again.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Mon May 05 22:01:30 2025 UTC