That's a mistake. Unless, that is, you are deliberately trying to speed up load times by canceling the images. Are you? Yes, bypass No... didn't know I only clicked on some button.
Is it because you find downloading images takes too long?
Yes
Yes, Much too
long!
No
Because if you think it IS too long, we might do something about it.
If you just want to bypass the images, the "OPTIONS" menu on your browser should let you re-configure it so that it will ask if you want images, or simply ignore them. Of course, you could use LYNX, but that doesn't do the type fonts.
If the url ends in a "/", it indicates to the server, (where all the text and images are stored,) that it should send you the existing index file for that subdirectory, or create a new index file for you if one does not exist.
BUT if the slash is at the end of an ."html/" (or ",htm") file, which is a TEXT file, then your browser incorrectly assumes that the file is a subdirectory, and that the images will be in that subdirectory. So when it sends the server a request for the images from, say ".../hot/index.html/" it will send for, say ".../hot/index.html/cath75.gif", and the server at Mall-Net finds that index.html is not a directory, and so it sends back a "500" level error code to your browser. (Totally wacko request.)
When your browser gets the message there is no such image, it then uses that lumpy image of a torn photo or a photo of a question mark instead. The server also gives us an error report in our logs, and when this happens over and over, we wonder if someone has bad URL's pointing to us, or if we screwed up someplace.
If you did use a URL that had the slash on the end, would you please tell use where it was.
Do you have any idea what these guys run up in cleaning bills?!?!?!
(Not to mention bug spray.)
So please, if you don't want images, use the OPTIONS menu to reconfigure your browser. If you do, make sure that there is not slash after the ".html".