معنی این نوشته ها در فایل access.log اسکوئید چیه؟

[Ronin]

GET
POST
DIRECT
TCP_IMS_HIT
TCP_SWAPFAIL_MISS
TCP_DENIED_REPLY
TCP_DENIED
TCP_MEM_HIT
TCP_REFRESH_UNMODIFIED

---

موضوعات مشابه:

• چرا گزینه control access through Remote Access Policy غیر فعاله؟
• خطای No Internet access هنگام شیر کردن اینترنت به وسیله access point در win7
• access for everyone
• باگ خطرناک در ACCESS
• مشکل انتقال از Access به SQL

---

[ghobar]

بهتر بود کمی از اون نوشته ها که منظورتون هست رو هم میزاشتید .

[M-r-r]

اگر سری به رفرنس های squidبزنید، نوشته شده :

6.5 Cache Result Codes

Note, TCP_ refers to requests on the HTTP port (3128).

TCP_HIT

A valid copy of the requested object was in the cache.
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_" refers to requests on the ICP port (3130)

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.

"ERR_" refers to various types of errors for HTTP requests.

6.6 Peer Status Coces

Hierarchy Data Tags

DIRECT The object has been requested from the origin
server.
FIREWALL_IP_DIRECT The object has been requested from the origin
server because the origin host IP address is
inside your firewall.
FIRST_PARENT_MISS The object has been requested from the
parent cache with the fastest weighted round
trip time.
FIRST_UP_PARENT The object has been requested from the first
available parent in your list.
LOCAL_IP_DIRECT The object has been requested from the origin
server because the origin host IP address
matched your 'local_ip' list.
SIBLING_HIT The object was requested from a sibling cache
which replied with a UDP_HIT.
NO_DIRECT_FAIL The object could not be requested because
of firewall restrictions and no parent caches
were available.
NO_PARENT_DIRECT The object was requested from the origin server
because no parent caches exist for the URL.
PARENT_HIT The object was requested from a parent cache
which replied with a UDP_HIT.
SINGLE_PARENT The object was requested from the only
parent cache appropriate for this URL.
SOURCE_FASTEST The object was requested from the origin server
because the 'source_ping' reply arrived first.
PARENT_UDP_HIT_OBJ The object was received in a UDP_HIT_OBJ reply
from a parent cache.
SIBLING_UDP_HIT_OBJ The object was received in a UDP_HIT_OBJ reply
from a sibling cache.
PASSTHROUGH_PARENT The neighbor or proxy defined in the config
option 'passthrough_proxy' was used.
SSL_PARENT_MISS The neighbor or proxy defined in the config
option 'ssl_proxy' was used.
DEFAULT_PARENT No ICP queries were sent to any parent
caches. This parent was chosen because
it was marked as 'default' in the config
file.
ROUNDROBIN_PARENT No ICP queries were received from any parent
caches. This parent was chosen because
it was marked as 'default' in the config
file and it had the lowest round-robin use
count.
CLOSEST_PARENT_MISS This parent was selected because it
included the lowest RTT measurement to
the origin server. This only appears
with 'query_icmp on' set in the config
file.
CLOSEST_DIRECT The object was fetched directly from the
origin server because this cache measured
a lower RTT than any of the parent caches.

Almost any of these may be preceeded by 'TIMEOUT_' if the two-second (default) timeout occurs waiting for all ICP replies to arrive from neighbors.
6.7 HTTP status codes

These are taken from RFC 2068.

100 Continue
101 Switching Protocols
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
303 See Other
304 Not Modified
305 Use Proxy
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Time-out
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Large
415 Unsupported Media Type
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Time-out
505 HTTP Version not supported

موفق باشید .

[Ronin]

خیلی ممنون(حبستو می کشیم)

[M-r-r]

خواهش دوست خوب من.