From:             [EMAIL PROTECTED]
Operating system: FreeBSD 4.4-RELEASE
PHP version:      4.1.1
PHP Bug Type:     Unknown/Other Function
Bug description:  problems with include()

Whenever I include (or require) a page, using an http url as the file value
(i.e. include("http://www.its-explosive.net/~davey/info.php";);) I get this
header added to the top of the page I've included.

This does not happen when I use a relative path. 

http://www.its-explosive.net/~davey/header.php show what happen when I
include the file info.php using a http url to it.

---
<?php include("http://www.its-explosive.net/~davey/header.php";); ?>
---
 
The contents of info.php are "<?php phpinfo(); ?>". 
http://www.its-explosive.net/~davey/noheader.php shows what happens when I
include it using the relative path:

---
<?php include("info.php"); ?>
---

The only difference (in case you didn't go, or you missed it) is the
text:

---
X-Powered-By: PHP/4.1.1 Connection: close Content-Type: text/html
---

is just added onto the top.

If you goto the urls you will see my phpinfo(); and can perhaps glean some
othre info from there.

I do know that if someone else includes my PHP files in their website
using the include("http://...";); code they also see the x-powered-by
header...

I've been looking around for a solution to this for weeks, I bet it's
something simple, but I just can't find it.

I hope you can help

- Davey
-- 
Edit bug report at http://bugs.php.net/?id=15667&edit=1
-- 
Fixed in CVS:        http://bugs.php.net/fix.php?id=15667&r=fixedcvs
Fixed in release:    http://bugs.php.net/fix.php?id=15667&r=alreadyfixed
Need backtrace:      http://bugs.php.net/fix.php?id=15667&r=needtrace
Try newer version:   http://bugs.php.net/fix.php?id=15667&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=15667&r=support
Expected behavior:   http://bugs.php.net/fix.php?id=15667&r=notwrong
Not enough info:     http://bugs.php.net/fix.php?id=15667&r=notenoughinfo
Submitted twice:     http://bugs.php.net/fix.php?id=15667&r=submittedtwice

Reply via email to