If you get to the page via the path:
then you don't get the pictures.
But if you get to the page via the path:
then you do get the pictures.
The difference is that in the first case
there is a slash at the end of the path.
Which is a mistake.
The reason that the slash prevents the images from appearing,
but doesn't affect getting the page, is the following:
The slash at first makes the server think that the path given it,
is to the non-existant folder:
When an HTML server is given a path to a folder,
it looks for a file named 'index.html' in the folder, to serve up.
So in this case the server first looks for:
Which it can't find.
But then the server is smart enough to guess
that maybe the slash was a mistake.
So it removes the slash, and looks for a page: "lian.html",
in the root folder: http://www.leonardcohenfiles.com/
Which it finds. And serves up.
But now the real problem begins,
- on the "client" side.
Our browsers (IE7 anyway) ought to,
but apparently don't, realize
that the server removed that slash.
They ought to realize it, because the server does inform the browser
where it actually found the page, vs how the browser had addressed it.
But apparently our browser stupidly assumes, instead,
that the page was actually found where it was (erroneously)
So in this case our browser thinks that the server
actually found the "lian.html" page in that imaginary folder:
So then, when our browser asks the server for the images,
---all of which happen to be specified via "relative links"
in the HTML of the page ---
it asks the server to look for them in that imaginary folder!!!
The server can't know or guess that it's a mistake, this time.
(That only works for urls to HTML pages.)
The only thing it can do is to tell the browser
that it can't find the images where specifed.
And so the browser has to put up red-xs instead.
For example, the first image in "lian.html"
is addressed as <IMG SRC="U2lc-1.jpg">
And our browser prepends to that what it thinks
is the path to the folder that the server found
"lian.html" in. That is, our browser asks
the server to return the image at:
Which the server can't find.
Beause the image is actually at:
When you get these red-xs, right-click on them,
and click "properties", and check out the "Address (URL)".
That's where your browser thinks the image ought to be.
In this case, erroneously: