Re: gif caching

Lile Elam ((no email))
Tue, 8 Oct 1996 16:36:20 -0700

> Date: Sun, 29 Sep 1996 11:45:15 -0700
> X-Sender: sarabel@pop.sirius.com
> To: artists@art.net
> From: sarabel@sirius.com (Patricia Corrigan)
> Subject: gif caching
> Content-Length: 459
>
> Is this happening to you?
>
> Over a week ago I removed or changed the titles of several gifs with "nude"
> in the title, but I'm getting more and more hits on them anyway. In other
> words, they're still there even though I've removed them.
>

Hi Sarabel,

Poeple can try to access files that no longer exist in your studio but
will just receive an error instead of the file. If you see 404 towards
the end of the logged entry, you know it failed. If you get a 200 it was
successful. A 304 means the file was catched on their system disk.

For instance, below is a failed access:

bass.lance.colostate.edu - - [07/Oct/1996:00:15:05 -0700] "GET /Studios/Visual/Sarabel/Three_nudes_view.gif HTTP/1.0" 404 -

Notice the 404 and - at the end. The 404 means that it failed and the
- means no bytes were transmitted.

The following is a successful file access from your space:

cust93.max7.detroit.mi.ms.uu.net - - [07/Oct/1996:00:00:12 -0700] "GET /Studios/Visual/Sarabel/Apple.gif HTTP/1.0" 200 1774

Notice the 200 and the 1774 at the end of the line. The 200 means that
it was successful and the 1774 means that how many bytes the file was.

> This mean to me that I have lost control of my web site. I'm not happy
> about this.
>

You have complete control over your space and what people can see there.
The log files can be confussing, we know. Sorry about this.

Let us know if you have any questions or concerns.

thanks,

-lile
(a webmaster@art.net)