|
|
Posted by Harlan Messinger on 11/20/07 19:29
Harlan Messinger wrote:
> John Salerno wrote:
>> Harlan Messinger wrote:
>>
>>> How can this have worked before? If, previously, your pages were
>>> directly under gestalt.johnjsal.com, then the ".." would have
>>> referred to a nonexistent parent directory.
>>>
>>> As for now, the ".." would take you up to the parent of the gestalt
>>> directory, but perhaps the web server has been configured (for
>>> security reasons) not to allow use of the parent operator "..".
>>
>> Well, the link was gestalt.johnjsal.com, but I guess that was just an
>> alias for www.johnjsal.com/gestalt, because the directory structure
>> was the same as it is now.
>
> If before your pages were under gestalt.johnjsal.com and now they are
> under www.johnjsal.com/gestalt, then the directory structure was not the
> same as it is now because before your pages were in the root and now
> they are one directory down. I think your point is that *within* your
> pages the structure is the same, or even that they haven't even been
> moved within the server's physical directory structure, but that's
> beside the point. What matters is the logical *website* structure. If
> you previously navigated to http://gestalt.johnjsal.com/x.y and that's
> the address that continued to appear in the browser's address field
> after the page loaded, then that means that there *was* no parent
> directory: the root doesn't have a parent directory. This technically
> made ".." meaningless. At best, the web server would have treated the
> root as its own parent--but that *isn't* the case now: with your pages
> one level down, the parent directory is the root directory, which is now
> *different* from the directory containing the pages.
Let me make this clearer. If the current page is
http://example.com/x.y
and it has an href on it that reads
"../a.b"
this will either be treated as a bad address or as
http://example.com/a.b
If the same page is now at the address
http://example.com/foo/x.y
then the href "../a.b" will be treated as
http://example.com/a.b
unless parent directories aren't allowed, in which case who knows how
this will be treated.
Navigation:
[Reply to this message]
|