Will new Domain affect virtual include?

[jason]

I am getting twisted by the possibility that my virtual includes which
currently work great on non-domain remote IP will crash if I purchase a
domain and point it to one of my designated folders.....Here is the scenario
and question::

If my remote webhost at (eg):

http://69.8.9.9

....has a subfolder with with:

cats/index.asp

....which consumes VIRTUAL INCLUDE:

<!--#includes virtual="/cats/forms/frm_boat.asp"-->
....If I then point the domain: www.cats.com to the subfolder:
http://69.8.9.9/cats/ondex.asp

* ...will my VIRTUAL FILE STILL WORK?? *

OR

....will it no longer assume that http://69.8.9.9 is the root and assume that
/cats/ is the root

I can't seem to get my head around this

[Ray at]

virtual include will just look at the structure of the site and include in
that way. So, if yoursite/cats/forms/frm_boat.asp is a valid url, you can
virtually include it regardless of what you do, unless I'm not comprehending
what you're doing. There will be two sites?

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl...

I am getting twisted by the possibility that my virtual includes which
currently work great on non-domain remote IP will crash if I purchase a
domain and point it to one of my designated folders.....Here is the scenario and question::

If my remote webhost at (eg):

http://69.8.9.9

...has a subfolder with with:

cats/index.asp

...which consumes VIRTUAL INCLUDE:

<!--#includes virtual="/cats/forms/frm_boat.asp"-->
...If I then point the domain: www.cats.com to the subfolder:
http://69.8.9.9/cats/ondex.asp

* ...will my VIRTUAL FILE STILL WORK?? *

OR

...will it no longer assume that http://69.8.9.9 is the root and assume that /cats/ is the root

I can't seem to get my head around this

[jason]

I'm probably not explaining correctly but at the moment my virtual includes
in a sub folder on a current IP (69.9.9..9) works...

But I am concerned that when I make one of my sub-folders LIVE with a domain
on this IP address my virtual includes will fall apart because they will no
longer reference from the root of the mother IP (which holds many sites) and
think the root is actually the sub-folder...

"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:eP**************@TK2MSFTNGP09.phx.gbl...

virtual include will just look at the structure of the site and include in
that way. So, if yoursite/cats/forms/frm_boat.asp is a valid url, you can
virtually include it regardless of what you do, unless I'm not comprehending what you're doing. There will be two sites?

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl...

I am getting twisted by the possibility that my virtual includes which
currently work great on non-domain remote IP will crash if I purchase a
domain and point it to one of my designated folders.....Here is the

scenario

and question::

If my remote webhost at (eg):

http://69.8.9.9

...has a subfolder with with:

cats/index.asp

...which consumes VIRTUAL INCLUDE:

<!--#includes virtual="/cats/forms/frm_boat.asp"-->
...If I then point the domain: www.cats.com to the subfolder:
http://69.8.9.9/cats/ondex.asp

* ...will my VIRTUAL FILE STILL WORK?? *

OR

...will it no longer assume that http://69.8.9.9 is the root and assume

that

/cats/ is the root

I can't seem to get my head around this

[Ray at]

I think I understand. So, just speaking of normal pages, a page that is
currently:

http://69.9.9.9/subdir/page.asp
will become
http://yourdomain.com/page.asp

If so, the virtual includes will fail. If you were to switch to file
includes, you'd be okay.

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:Os**************@TK2MSFTNGP10.phx.gbl...

I'm probably not explaining correctly but at the moment my virtual includes in a sub folder on a current IP (69.9.9..9) works...

But I am concerned that when I make one of my sub-folders LIVE with a domain on this IP address my virtual includes will fall apart because they will no longer reference from the root of the mother IP (which holds many sites) and think the root is actually the sub-folder...

"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:eP**************@TK2MSFTNGP09.phx.gbl...

virtual include will just look at the structure of the site and include in that way. So, if yoursite/cats/forms/frm_boat.asp is a valid url, you can virtually include it regardless of what you do, unless I'm not

comprehending

what you're doing. There will be two sites?

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl...

I am getting twisted by the possibility that my virtual includes which
currently work great on non-domain remote IP will crash if I purchase a domain and point it to one of my designated folders.....Here is the

scenario

and question::

If my remote webhost at (eg):

http://69.8.9.9

...has a subfolder with with:

cats/index.asp

...which consumes VIRTUAL INCLUDE:

<!--#includes virtual="/cats/forms/frm_boat.asp"-->
...If I then point the domain: www.cats.com to the subfolder:
http://69.8.9.9/cats/ondex.asp

* ...will my VIRTUAL FILE STILL WORK?? *

OR

...will it no longer assume that http://69.8.9.9 is the root and

assume that

/cats/ is the root

I can't seem to get my head around this

[jason]

Damn! This is soooo tricky to do if you are deep in the folder structure -
in fact its a nightmare to use relative paths - I suppose I could use the IP
address in the virtual include to stop the include failing....

How do you normally work out relative FILE paths if you are deep inside the
folder structure?

Thanks
Jason
"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:ux**************@TK2MSFTNGP09.phx.gbl...

I think I understand. So, just speaking of normal pages, a page that is
currently:

http://69.9.9.9/subdir/page.asp
will become
http://yourdomain.com/page.asp

If so, the virtual includes will fail. If you were to switch to file
includes, you'd be okay.

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:Os**************@TK2MSFTNGP10.phx.gbl...

I'm probably not explaining correctly but at the moment my virtual includes

in a sub folder on a current IP (69.9.9..9) works...

But I am concerned that when I make one of my sub-folders LIVE with a

domain

on this IP address my virtual includes will fall apart because they will

no

longer reference from the root of the mother IP (which holds many sites)

and

think the root is actually the sub-folder...

"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:eP**************@TK2MSFTNGP09.phx.gbl...

virtual include will just look at the structure of the site and include in

that way. So, if yoursite/cats/forms/frm_boat.asp is a valid url, you can virtually include it regardless of what you do, unless I'm not comprehending

what you're doing. There will be two sites?

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl...
>
> I am getting twisted by the possibility that my virtual includes

which > currently work great on non-domain remote IP will crash if I

purchase a > domain and point it to one of my designated folders.....Here is the
scenario
> and question::
>
> If my remote webhost at (eg):
>
> http://69.8.9.9
>
> ...has a subfolder with with:
>
> cats/index.asp
>
> ...which consumes VIRTUAL INCLUDE:
>
> <!--#includes virtual="/cats/forms/frm_boat.asp"-->
>
>
> ...If I then point the domain: www.cats.com to the subfolder:
> http://69.8.9.9/cats/ondex.asp
>
> * ...will my VIRTUAL FILE STILL WORK?? *
>
> OR
>
> ...will it no longer assume that http://69.8.9.9 is the root and assume that
> /cats/ is the root
>
> I can't seem to get my head around this
>
>

[Ray at]

You could do a find and replace on all your ASP pages using your favorite
text editor (which should be www.textpad.com) and replace /cats/ with /.

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...

Damn! This is soooo tricky to do if you are deep in the folder structure -
in fact its a nightmare to use relative paths - I suppose I could use the IP address in the virtual include to stop the include failing....

How do you normally work out relative FILE paths if you are deep inside the folder structure?

Thanks
Jason

[jason]

That's not the problem - my problem is working out the PATH for the new FILE
includes which could go something like this:
..../../../../../forms/forma.asp

....It is really difficult to work out the PATH - is there a simple way to do
this?
"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:O7*************@TK2MSFTNGP10.phx.gbl...

You could do a find and replace on all your ASP pages using your favorite
text editor (which should be www.textpad.com) and replace /cats/ with /.

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...

Damn! This is soooo tricky to do if you are deep in the folder structure - in fact its a nightmare to use relative paths - I suppose I could use

the IP

address in the virtual include to stop the include failing....

How do you normally work out relative FILE paths if you are deep inside

the

folder structure?

Thanks
Jason

[Ray at]

I know, but right now you have virtual includes. I'm saying you can keep
your virtual includes by replacing /cat/ with /. Do you ~want~ to switch to
file includes with relative physical paths like that?

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:O2**************@TK2MSFTNGP09.phx.gbl...

That's not the problem - my problem is working out the PATH for the new FILE includes which could go something like this:
.../../../../../forms/forma.asp

...It is really difficult to work out the PATH - is there a simple way to do this?
"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:O7*************@TK2MSFTNGP10.phx.gbl...

You could do a find and replace on all your ASP pages using your favorite

text editor (which should be www.textpad.com) and replace /cats/ with /.

Ray at work

"jason" <ja***@catamaranco.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...

Damn! This is soooo tricky to do if you are deep in the folder structure - in fact its a nightmare to use relative paths - I suppose I could use

the

IP

address in the virtual include to stop the include failing....

How do you normally work out relative FILE paths if you are deep

inside the

folder structure?

Thanks
Jason