Help on HTML and Relative URL's?

I am modifying some html code that was originally developed by someone else on a
MAC using Dreamweaver. The following line is an example of a some code that I'm
having a problem with:

<A HREF="../schedule.htm"> Scheduled Hours </A>

In my limited knowledge of HTML, ../ means look in one directory up for the file
schedule.htm. However, on my local PC, schedule.htm is in the current directory
so it can't be found. Perhaps there is some setting in Dreamweaver that makes it
work.

What I don't understand is if I upload this to a cpanel web-host in the
directory public_html, along with all of the other HTM files, it works okay.
That is, it appears that in cpanel the ../ is ignored and the code works okay.

Questions:

1. Why does it (the ../) work in cpanel but not on my local computer?

2. Is there some setting in Dreamweaver that allows this to work on a local
computer?

I know the simple answer to this is to go through all of the code and delete all
appearances of ../

On Sun, 03 Apr 2005 1133 -0400, Arnie Goetchius
<arnie.goetchius@att.net> wrote:

> 1. Why does it (the ../) work in cpanel but not on my local computer?

If such a link is online and is in the root directory, conforming clients
should see this and search for the file in the root directory. Failing
that, a conforming server should not let HTTP requests move above the
"public html" folder and thus should discard the "../".

When you put this link on your local computer, neither of these failsafe's
exist.

> 2. Is there some setting in Dreamweaver that allows this to work on a
> local computer?

I wouldn't know. It's best to fix the erronious link so it works properly
in both places, IMHO.

> I know the simple answer to this is to go through all of the code and
> delete all appearances of ../

You got it.

Grey

--
The technical axiom that nothing is impossible sinisterly implies the
pitfall corollary that nothing is ridiculous.
- http://www.greywyvern.com/webslavent?msg=149 - Presto the Puffin!

GreyWyvern wrote:

> On Sun, 03 Apr 2005 1133 -0400, Arnie Goetchius
> <arnie.goetchius@att.net> wrote:
>
>> 1. Why does it (the ../) work in cpanel but not on my local computer?
>
>
> If such a link is online and is in the root directory, conforming
> clients should see this and search for the file in the root directory.
> Failing that, a conforming server should not let HTTP requests move
> above the "public html" folder and thus should discard the "../".
>
> When you put this link on your local computer, neither of these
> failsafe's exist.
>
>> 2. Is there some setting in Dreamweaver that allows this to work on a
>> local computer?
>
>
> I wouldn't know. It's best to fix the erronious link so it works
> properly in both places, IMHO.
>
>> I know the simple answer to this is to go through all of the code and
>> delete all appearances of ../
>
>
> You got it.
>
> Grey
>

Thanks for the explanation. I'll fix it. It's a mystery to me how the original
author could have viewed this properly on a MAC.

On 2005-04-03 1259 -0400, Arnie Goetchius <arnie.goetchius@att.net> said:

> Thanks for the explanation. I'll fix it. It's a mystery to me how the
> original author could have viewed this properly on a MAC.



It's Mac, not MAC (MAC is a Media Access Control address, and relates
to ethernet hardware), but to answer your question, the developer was
most likely using Apache (standard on all Macs) which is a a
'conforming' server, and would handle the ../ removal properly.

just remove it completely and all should be good.

Ben Jamieson wrote:
> On 2005-04-03 1259 -0400, Arnie Goetchius <arnie.goetchius@att.net>
> said:
>
>> Thanks for the explanation. I'll fix it. It's a mystery to me how the
>> original author could have viewed this properly on a MAC.
>
>
>
>
> It's Mac, not MAC (MAC is a Media Access Control address, and relates to
> ethernet hardware), but to answer your question, the developer was most
> likely using Apache (standard on all Macs) which is a a 'conforming'
> server, and would handle the ../ removal properly.
>
> just remove it completely and all should be good.
>

Okay, understand. Thanks for responding.