Analisa Access.log squid

TCP_HIT
Sebuah salinan sah dari objek yang diminta dalam cache.

TCP_MEM_HIT
Sebuah salinan sah dari objek yang diminta dalam cache, DAN itu berada di
memori sehingga tidak harus dibaca dari disk.

TCP_NEGATIVE_HIT
Permintaan itu untuk objek negatif-cache. Negatif-caching mengacu
kepada caching jenis tertentu kesalahan, seperti Jumlah "404 Tidak Ditemukan."
waktu kesalahan ini cache dikontrol dengan negative_ttl
parameter konfigurasi.

TCP_MISS
Objek yang diminta tidak dalam cache.

TCP_REFRESH_HIT
Benda itu dalam cache, namun basi. Permintaan Jika-Diubah-Sejak itu
dibuat dan "304 Not Modified" balasan telah diterima.

TCP_REF_FAIL_HIT
Benda itu dalam cache, namun basi. Permintaan untuk memvalidasi objek
gagal, sehingga objek (basi) tua itu kembali.

TCP_REFRESH_MISS
Benda itu dalam cache, namun basi. Permintaan Jika-Diubah-Sejak itu
dibuat dan membalas yang terkandung konten baru.

TCP_CLIENT_REFRESH
Klien mengeluarkan permintaan dengan pragma "no-cache".

TCP_IMS_HIT
Klien mengeluarkan Jika-Diubah-Sejak permintaan dan objek berada di
cache dan masih segar.

TCP_IMS_MISS
Klien mengeluarkan Jika-Diubah-Sejak permintaan untuk objek basi.

TCP_SWAPFAIL
Benda itu diyakini berada di cache, namun tidak dapat diakses.

TCP_DENIED
Akses ditolak untuk permintaan ini

UDP_HIT
Sebuah salinan sah dari objek yang diminta dalam cache.

UDP_HIT_OBJ
Sama seperti UDP_HIT, namun data objek itu cukup kecil untuk dikirim dalam UDP
balasan paket. Menyimpan permintaan TCP berikut.

UDP_MISS
Objek yang diminta tidak dalam cache.

UDP_DENIED
Akses ditolak untuk permintaan ini.

UDP_INVALID
Permintaan tidak valid diterima.

UDP_RELOADING
Permintaan ICP adalah "menolak" karena cache sibuk reload metadata nya.


analysis Access.log squid

TCP_HIT
A valid copy of the requested object was in the cache.

TCP_MEM_HIT
A valid copy of the requested object was in the cache, AND it was in
memory so it did not have to be read from disk.

TCP_NEGATIVE_HIT
The request was for a negatively-cached object. Negative-caching refers
to caching certain types of errors, such as “404 Not Found.” The amount
of time these errors are cached is controlled with the negative_ttl
configuration parameter.

TCP_MISS
The requested object was not in the cache.

TCP_REFRESH_HIT
The object was in the cache, but STALE. An If-Modified-Since request was
made and a “304 Not Modified” reply was received.

TCP_REF_FAIL_HIT
The object was in the cache, but STALE. The request to validate the object
failed, so the old (stale) object was returned.

TCP_REFRESH_MISS
The object was in the cache, but STALE. An If-Modified-Since request was
made and the reply contained new content.

TCP_CLIENT_REFRESH
The client issued a request with the “no-cache” pragma.

TCP_IMS_HIT
The client issued an If-Modified-Since request and the object was in the
cache and still fresh.

TCP_IMS_MISS
The client issued an If-Modified-Since request for a stale object.

TCP_SWAPFAIL
The object was believed to be in the cache, but could not be accessed.

TCP_DENIED
Access was denied for this request

UDP_HIT
A valid copy of the requested object was in the cache.

UDP_HIT_OBJ
Same as UDP_HIT, but the object data was small enough to be sent in the UDP
reply packet. Saves the following TCP request.

UDP_MISS
The requested object was not in the cache.

UDP_DENIED
Access was denied for this request.

UDP_INVALID
An invalid request was received.

UDP_RELOADING
The ICP request was “refused” because the cache is busy reloading its metadata.