This made absolutely no sense to me.  If someone else can make sense of this, feel free to unbogus it.

What in the world do you mean by, "A PHP file that includes a local file via a HTTP header request" ?

As in header('Location: http://local.domain/file.php') ?

That is a client-side redirect which means the remote browser is going to make a completely separate request which may or may not come back to the same process or even the same physical server in a load-balanced architecture.  Expecting any sort of variable persistency across client-side redirects is rather silly.  This is what sessions are for.

Rasmus the HTTP header request is used in all PHP methods that request a file with a HTTP or full LINK even if it is local.

Such as fopen(), file(), readfile(), include, require, include_once, require_once. All of these can include files with a absolute URI.

FYI, Sessions don't persist from one http session to another even inside the same domain when one file is included within another via a absolute url.

I don't understand why you call this a header http request, but whatever.  So you want 
include 'http://local.domain/file.php'
to act like
include 'file.php'
if local.domain happens to be the a local domain?  Seems to me like this is something that you should be checking at the application level.  Why use a url when the file is local?  We could add a check, but it would add extra dns calls to every url file operation and I don't think it is worth it.

Oh, and to get your sessions to persist across a url file open, simply pass your SID along.

You're right about the additional load it would add and yes you can pass variables via the Query string.

For me the feature request is more technical in nature than cosmetic patches will cover.

When you execute a script and during its run I include'http://samedomain/file.php' There are limitations of scope that are placed on the included local file in comparison to its parent file which to me seems unecessary.

This ruins the code flow for me, practically and mentally.

I wonder if this is part of the child process limitation in PHP?

But you still haven't answered why you are doing:
include 'http://samedomain/file.php';
This makes no sense to me.  Why go through HTTP when the file is local?

Specifically, for me as I said it is about code flow and options.

Really as simple as that. Having the ability to include a file with its full URI that makes a new header request without losing variable scope (locally) of the previous header request it is inside of would be beneficial to me and my php development by allowing me to gain more freedom and options.

Options I think is the key word that this would create for me. Variables give me options losing them in middle of a run takes away my options.

If there were to be any considertion for something like this, I would suggest a PREFIX optional argument that would prepend the newly created ENV variables from the new and second header request within the same domain.

Maybe you're not clear on what I am suggesting.

I am requesting the ability to include a full URL and a new header request within an existing header request on the same domain, same script execution run, that enables me to have two or more sets of unique and shared variables without losing variable scope.

Oh, I understand what you are asking for, it just still makes absolutely no sense to me.  Why would you incur the overhead of an unneccesary HTTP request just for code flow?  Wrap your include function yourself then.

function my_include($url) {
    $a = parse_url($url);
    if($a['host'] == $_SERVER['SERVER_NAME'] {
        $file = $_SERVER['DOCUMENT_ROOT'].$a['path'];
    } else $file = $url;
    include $file;
}

my_include('http://localdomain/file.php');

That's all.  Building this into PHP doesn't make any sense to me.

Its just a feature request not a direct order.

The feature request is not how to do includes but rather how to maintain the integrity of variable scopes when including a new http header request (while wanting all those new variables) inside an existing header request (while maintaining all those existing variables into the new header request).

This is not something you can code hack to replicate it is an intrinsic sub request or child process that would establish user defined optional prefix based env variable differentials.

But if you turn the include into a normal file-system based include as I illustrated in my_include() then variables are maintained.  Locally included files share the same scope as the script doing the inclusion.  I see no use for what you are asking for, sorry.

No biggie, I was planning on porting my development to Zope eventually anyways.

Thanks for your attention to detail and quick responses.

I agree with rasmus not to build it into php.