say i have two domain names - adomain.com and anotherdomain.com.
adomain.com's base directory is the same as
anotherdomain.com/~adomain/. if i were running a php script on
adomain.com, how might i determe the real path of that php script (ie.
not the virtual path)?

On 3 Mar 2005 21:21:04 -0800, yawnmoth <terra1024@yahoo.com> wrote:
> say i have two domain names - adomain.com and anotherdomain.com.
> adomain.com's base directory is the same as
> anotherdomain.com/~adomain/. if i were running a php script on
> adomain.com, how might i determe the real path of that php script (ie.
> not the virtual path)?

Why not make a sample script that prints all env variables to find out?
I am not familiar with php, but judging from CGI, you might get something
useful from SCRIPT_FILENAME

David Efflandt wrote:
> On 3 Mar 2005 21:21:04 -0800, yawnmoth <terra1024@yahoo.com> wrote:
> > say i have two domain names - adomain.com and anotherdomain.com.
> > adomain.com's base directory is the same as
> > anotherdomain.com/~adomain/. if i were running a php script on
> > adomain.com, how might i determe the real path of that php script
(ie.
> > not the virtual path)?
>
> Why not make a sample script that prints all env variables to find
out?
> I am not familiar with php, but judging from CGI, you might get
something
> useful from SCRIPT_FILENAME

i did. here's the contents of that script:

<?
print_r($_ENV);
echo '<p>--<p>';
print_r($_SERVER);
?>

nothing that was printed out showed the real path - only the virtual
paths (or the filesystem paths, which i can't use to construct
alternative url's from).

yawnmoth <terra1024@yahoo.com> wrote:
> nothing that was printed out showed the real path - only the virtual
> paths (or the filesystem paths, which i can't use to construct
> alternative url's from).

What about using one or more of DOCUMENT_ROOT, REQUEST_URI, and
SERVER_NAME?

Chris

chris-usenet@roaima.co.uk wrote:
> yawnmoth <terra1024@yahoo.com> wrote:
> > nothing that was printed out showed the real path - only the
virtual
> > paths (or the filesystem paths, which i can't use to construct
> > alternative url's from).
>
> What about using one or more of DOCUMENT_ROOT, REQUEST_URI, and
> SERVER_NAME?
>
> Chris

the real path: /~adomain/
DOCUMENT_ROOT: /home/adomain/
REQUEST_URI: /
SERVER_NAME: www.adomain.com

that's when i view the webpage by going to adomain.com.

when i view the webpage by going to anotherdomain.com/~adomain/, i get
the information that i want, but at that point, i already know it, so
such a lookup is pointless. i want to determine the real path when i'm
accessing the webpage from adomain.com.

> chris-usenet@roaima.co.uk wrote:
>> yawnmoth <terra1024@yahoo.com> wrote:
>> > nothing that was printed out showed the real path - only the
> virtual
>> > paths (or the filesystem paths, which i can't use to construct
>> > alternative url's from).
>>
>> What about using one or more of DOCUMENT_ROOT, REQUEST_URI, and
>> SERVER_NAME?
>>
>> Chris

yawnmoth <terra1024@yahoo.com> wrote:
> the real path: /~adomain/

> DOCUMENT_ROOT: /home/adomain/
> REQUEST_URI: /
> SERVER_NAME: www.adomain.com

> that's when i view the webpage by going to adomain.com.

Yes. All good so far. And when you run the same script via the other
domain...?

> when i view the webpage by going to anotherdomain.com/~adomain/, i get
> the information that i want, but at that point, i already know it, so
> such a lookup is pointless. i want to determine the real path when i'm
> accessing the webpage from adomain.com.

Now I'm totally confused. Two of us have suggested the relevant variables
to you, a combination of which should tell you everything you need to
know about the server name, the request URI and the real script path,
yet this isn't enough.

Somewhere either you've not explained yourself sufficiently or one of
the three of us has misunderstood. Same net effect.

Chris

On 4 Mar 2005 08:33:54 -0800, yawnmoth <terra1024@yahoo.com> wrote:
>
> chris-usenet@roaima.co.uk wrote:
>> yawnmoth <terra1024@yahoo.com> wrote:
>> > nothing that was printed out showed the real path - only the
> virtual
>> > paths (or the filesystem paths, which i can't use to construct
>> > alternative url's from).
>>
>> What about using one or more of DOCUMENT_ROOT, REQUEST_URI, and
>> SERVER_NAME?
>>
>> Chris
>
> the real path: /~adomain/
> DOCUMENT_ROOT: /home/adomain/
> REQUEST_URI: /
> SERVER_NAME: www.adomain.com
>
> that's when i view the webpage by going to adomain.com.
>
> when i view the webpage by going to anotherdomain.com/~adomain/, i get
> the information that i want, but at that point, i already know it, so
> such a lookup is pointless. i want to determine the real path when i'm
> accessing the webpage from adomain.com.

The real path is the absolute (full) system path. Any URL or URI path is
a virtual path that you used to access the resource. How do you propose
for 1 virtual host to know the URL path via another virtual host unless
you include that info in the script itself (it is NOT going to be in env
automatically).