symbolic links weirdness?

m wrote:
 > I browsed into:
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://www.tek-tips.com/gthreadminder.cfm/lev2/67/lev3/</font" target="_blank">http://www.tek-tips.com/gthreadminder.cfm/lev2/67/lev3/</font</a>>
 >
 > ...and discovered a very irritating bouncing popup window.
 > Nevertheless curious about its inner workings, I displayed the
 > source and learned that the .js file was at:
 >
 > <script language="JavaScript" SRC="jsource.js"
 > TYPE="text/javascript"></SCRIPT>
 >
 > ...so I enter 'jsource.js' at the end of the address to display
 > it in my browser, and get a 404 error. Bah!
 >
 > I eventually find it waaaay back at:
 >
<font color=purple> > <a style='text-decoration: underline;' href="http://www.tek-tips.com/jsource.js</font" target="_blank">http://www.tek-tips.com/jsource.js</font</a>>
 >
 > Is all the extra stuff in the original address:
 >
 > ...gthreadminder.cfm/lev2/67/lev3/
 >
 > done with symbolic links on a 'nix server? Other
 > possibilities?
 > (And please add your theory why anyone might want
 > to do this!)

As suspected, this is the problem (in the HTML source):
<base HREF="http://www.tek-tips.com/">

Basically, this indicates to the browser that all relative links are
relative to the root directory of the domain.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: symbolic links weirdness? 

David Venn-Brown wrote:

 >
 > As suspected, this is the problem (in the HTML source):
 > <base HREF="http://www.tek-tips.com/">
 >
 > Basically, this indicates to the browser that all relative links are
 > relative to the root directory of the domain.
 >
Thanks, David,I somehow missed that line when reading the source.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: symbolic links weirdness? 

"m" <noXwebxmasterx.DeleteThis@mbxstevensx.com> wrote in message
news:6eh4b.2931$Lk5.2882@newsread3.news.pas.earthlink.net...
 > m wrote:
 >
  > > I browsed into:
  > >
<font color=green>  > > <a style='text-decoration: underline;' href="http://www.tek-tips.com/gthreadminder.cfm/lev2/67/lev3/</font" target="_blank">http://www.tek-tips.com/gthreadminder.cfm/lev2/67/lev3/</font</a>>
  > >
  > > ...and discovered a very irritating bouncing popup window.
  > > Nevertheless curious about its inner workings, I displayed the
  > > source and learned that the .js file was at:
  > >
  > > <script language="JavaScript" SRC="jsource.js"
  > > TYPE="text/javascript"></SCRIPT>
  > >
  > > ...so I enter 'jsource.js' at the end of the address to display
  > > it in my browser, and get a 404 error. Bah!
  > >
  > > I eventually find it waaaay back at:
  > >
<font color=green>  > > <a style='text-decoration: underline;' href="http://www.tek-tips.com/jsource.js</font" target="_blank">http://www.tek-tips.com/jsource.js</font</a>>
  > >
  > > Is all the extra stuff in the original address:
  > >
  > > ...gthreadminder.cfm/lev2/67/lev3/
  > >
  > > done with symbolic links on a 'nix server? Other
  > > possibilities?
  > > (And please add your theory why anyone might want
  > > to do this!)
  > >
  > > Bemusidly,
  > > m
  > >
  > >
 > ...oh, and by the way, .cfm files turn out to be
 > something to do with ColdFusion...
Why did you add the js stuff to the end of the address? Clearly from the
script lang declaration it is in the home dir.

Anything after the .com/ can be an absolute or a relative. It can also be
aliased so for example, if the js source file is in the home dir but is used
by pages from different places (dir levels) then in order to use the one
file (instead of having dupes all over the place) it is far more efficient
to alias the source file as in this case it could be

alias /jsource.js /usr/local/etc/httpd/htdocs/jsource.js
the first bit is the alias name which appears at the end of the url and the
second part is the real name telling the server where on the machine to find
the file.

So, any call by a page will find the file regardless where on the server the
calling file is located.

The above is on Unix. the dir structure in linux is a little different but
the principle is the same and is fairly standard way of doing things.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: symbolic links weirdness?