ID: 38272
User updated by: djh146 at psu dot edu
Reported By: djh146 at psu dot edu
Status: Bogus
Bug Type: IIS related
Operating System: Windows 2000
PHP Version: 4.4.2
New Comment:
Bah! Simple issue. What was strange was that behavior was as expected
until a hardware replacement. Not sure how it was working until then!
Thanks
Previous Comments:
------------------------------------------------------------------------
[2006-07-31 18:36:54] [EMAIL PROTECTED]
That's pretty easy to explain:
your B instance has A's path in include_path, so when you use relative
path like "includes/header.php", PHP looks for "header.php" in its
include_path and finds the one from A.
This is apparently expected behaviour until you can prove I'm wrong
(we'd you to try PHP4.4.3 and provide a reproduce case in this case).
------------------------------------------------------------------------
[2006-07-31 18:28:06] djh146 at psu dot edu
Description:
------------
I am running PHP as a CGI under IIS 5. There are multiple web
instances running on the server. Two are PHP applications that use
include files (i.e. includes/header.php, includes/footer.php, etc.)
that are included on pages as <? include('includes/header.php') ?>.
Both applications use the same code structure.
When running these applications, I am seeing the include files from one
website instance appearing as the includes on another instance. It
appears to be only in one direction.
I encountered a similar problem when objects of the same name were
being treated ambigiously. This was discovered to be a problem
occuring using the ISAPI module in IIS and shared process space, which
is why I moved to the CGI configuration.
Could this be a similar problem? The two sites are running under the
same IP address with different headers, and the source for each are
located in seperate folders on the same drive.
Expected result:
----------------
The sites should (and have) run without interference from each other.
Actual result:
--------------
Site A's include header and footer will appear in Site B's output.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=38272&edit=1
