¿ù°£ Àα⠰Խù°

°Ô½Ã¹° 1,355°Ç
   
SQUID ij½Ã·Î±× °ª
±Û¾´ÀÌ : ÃÖ°í°ü¸®ÀÚ ³¯Â¥ : 2009-12-01 (È­) 10:48 Á¶È¸ : 22495
±ÛÁÖ¼Ò :
                                
(1) TCP_HIT, TCP_MEM_HIT
    ¿äûÇÑ ÄÁÅÙÃ÷°¡ ij½Ã¿¡ À־ ÀÀ´äÇÑ °æ¿ì


(2) TCP_MISS
    ¿äûÇÑ ÄÁÅÙÃ÷°¡ ij½Ã¿¡ ¾ø¾î¼­ ½ÇÁ¦ ¼­¹ö·Î ¿äûÀ» ÇÏ¿© ÀÀ´äÇÑ °æ¿ì


(3) TCP_IMS_HIT
    Å¬¶óÀ̾ðÆ®°¡ If-Modified-Since Çʵ带 ¿äû Çì´õ¿¡ º¸³Â´Âµ¥ HIT°¡ ³µ´Ù´Â ÀǹÌÀÌ´Ù.
    ¸¸¾à °á°ú HTTPÄڵ尪ÀÌ '304 Not Modified'·Î ³ª¿Ô´Ù¸é ij½Ã´Â
    Å¬¶óÀ̾ðÆ®·Î ÄÁÅÙÃ÷¸¦ º¸³¾ ÇÊ¿ä¾øÀÌ Å¬¶óÀ̾ðÆ® ºê¶ó¿ìÀú¿¡ ÀÖ´Â ÄÁÅÙÃ÷¸¦ »ç¿ëÇÑ´Ù´Â ÀǹÌÀÌ´Ù.


(4) TCP_IMS_MISS
    ¿äûÇì´õ¿¡ If-Modified-Since °¡ Æ÷ÇԵǾî ÀÖÁö¸¸ ij½Ã°¡ ½Å¼±ÇÏÁö ¾Ê´Ù°í ÆÇ´ÜµÇ¾î ½ÇÁ¦ ¼­¹ö·Î Àç¿äûÀ» ÇÑ °æ¿ì


(5) TCP_REFRESH_HIT
    ¿äûÇÑ ÄÁÅÙÃ÷°¡ ½Å¼±ÇÏÁö ¾Ê¾Æ ½ÇÁ¦ ¼­¹ö·Î ¿äûÇߴµ¥ '304 Not Modified'¸¦ ¹Þ¾Æ ij½Ã¿¡¼­ Ŭ¶óÀ̾ðÆ®·Î ÀÀ´äÇÑ °æ¿ì


(6) TCP_REFRESH_MISS
    ¿äûÇÑ ÄÁÅÙÃ÷°¡ ½Å¼±ÇÏÁö ¾Ê¾Æ ½ÇÁ¦ ¼­¹ö·Î ¿äûÇߴµ¥
    ¼­¹ö¿¡¼­ »õ·Î¿î ÄÁÅÙÃ÷¸¦ Àü¼Û¹Þ¾Æ ij½Ã¿¡ ÀúÀåÇÏ°í ´Ù½Ã Å¬¶óÀ̾ðÆ®·Î ÀÀ´ä


(7) TCP_CLIENT_REFRESH
    Å¬¶óÀ̾ðÆ® ¿äû Çì´õ¿¡ 'no_cache'¸¦ Æ÷ÇÔÇÑ °æ¿ì


(8) TCP_CLIENT_REFRESH_MISS
    Å¬¶óÀ̾ðÆ® ¿äû¿¡ 'no-cache'³ª 'no-store'°°Àº ij½Ã¸¦ Á¦¾îÇÏ´Â Çʵ带 Æ÷ÇÔÇÏ¿©¼­
    Ä³½Ã°¡ ¼­¹ö·ÎºÎÅÍ ÄÁÅÙÃ÷¸¦ °¡Á®¿ÔÀ»¶§


(9) TCP_DENIED 
    Å¬¶óÀ̾ðÆ® ¿äûÀÌ Ä³½Ã¿¡ ÀÇÇؼ­ °ÅÀý´çÇßÀ» °æ¿ì(ÄÁÅÙÃ÷ÇÊÅ͸µ°ú ¿¬°ü)
 
 
 
 

Cache Result Codes

TCP_ 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_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_ codes

"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_ codes

"ERR_" refers to various types of errors for HTTP requests. For example:
ERR_CLIENT_ABORT
The client aborted its request.
 
ERR_NO_CLIENTS
There are no clients requesting this URL any more.
 
ERR_READ_ERROR
There was a read(2) error while retrieving this object.
 
ERR_CONNECT_FAIL
Squid failed to connect to the server for this request.
 

Peer Status Codes

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 preceded by 'TIMEOUT_' if the two-second (default) timeout occurs waiting for all ICP replies to arrive from neighbors.

À̸§ Æнº¿öµå
ºñ¹Ð±Û (üũÇÏ¸é ±Û¾´À̸¸ ³»¿ëÀ» È®ÀÎÇÒ ¼ö ÀÖ½À´Ï´Ù.)
¿ÞÂÊÀÇ ±ÛÀÚ¸¦ ÀÔ·ÂÇϼ¼¿ä.
   

 



 
»çÀÌÆ®¸í : ¸ðÁö¸®³× | ´ëÇ¥ : ÀÌ°æÇö | °³ÀÎÄ¿¹Â´ÏƼ : ·©Å°´åÄÄ ¿î¿µÃ¼Á¦(OS) | °æ±âµµ ¼º³²½Ã ºÐ´ç±¸ | ÀüÀÚ¿ìÆí : mojily°ñ¹ðÀÌchonnom.com Copyright ¨Ï www.chonnom.com www.kyunghyun.net www.mojily.net. All rights reserved.