pfsense:squid:squid_result_codes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| pfsense:squid:squid_result_codes [2020/03/15 15:54] – peter | pfsense:squid:squid_result_codes [2020/07/15 09:30] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| These tags are optional and describe why the particular handling was performed or where the request came from: | These tags are optional and describe why the particular handling was performed or where the request came from: | ||
| - | |**CF**|At least one request in this transaction was collapsed. See collapsed_forwarding for more details about request collapsing. Support for this tag has been added to Squid v5 on 2018-06-18 (commit d2a6dc). It may not be available in earlier Squid versions.| | + | |**CF**|At least one request in this transaction was collapsed. See [[http:// |
| |**CLIENT**|The client request placed limits affecting the response. Usually seen with client issued a " | |**CLIENT**|The client request placed limits affecting the response. Usually seen with client issued a " | ||
| |**IMS**|The client sent a revalidation (conditional) request.| | |**IMS**|The client sent a revalidation (conditional) request.| | ||
| Line 19: | Line 19: | ||
| |**REFRESH**|A revalidation (conditional) request was sent to the server.| | |**REFRESH**|A revalidation (conditional) request was sent to the server.| | ||
| |**SHARED**|This tag is not supported yet. This request was combined with an existing transaction by collapsed forwarding. NOTE: the existing request is not marked as SHARED.| | |**SHARED**|This tag is not supported yet. This request was combined with an existing transaction by collapsed forwarding. NOTE: the existing request is not marked as SHARED.| | ||
| - | |**REPLY**|The HTTP reply from server or peer. Usually seen on DENIED due to http_reply_access ACLs preventing delivery of servers response object to the client.| | + | |**REPLY**|The HTTP reply from server or peer. Usually seen on **DENIED** due to [[http:// |
| Line 26: | Line 26: | ||
| |**NEGATIVE**|Only seen on HIT responses. Indicating the response was a cached error response. e.g. "404 not found" | |**NEGATIVE**|Only seen on HIT responses. Indicating the response was a cached error response. e.g. "404 not found" | ||
| |**STALE**|The object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error cache controls.| | |**STALE**|The object was cached and served stale. This is usually caused by stale-while-revalidate or stale-if-error cache controls.| | ||
| - | |**OFFLINE**|The requested object was retrieved from the cache during offline_mode. The offline mode never validates any object.| | + | |**OFFLINE**|The requested object was retrieved from the cache during |
| |**INVALID**|An invalid request was received. An error response was delivered indicating what the problem was.| | |**INVALID**|An invalid request was received. An error response was delivered indicating what the problem was.| | ||
| - | |**FAIL**|Only seen on REFRESH to indicate the revalidation request failed. The response object may be the server provided network error or the stale object which was being revalidated depending on stale-if-error cache control.| | + | |**FAIL**|Only seen on **REFRESH** to indicate the revalidation request failed. The response object may be the server provided network error or the stale object which was being revalidated depending on stale-if-error cache control.| |
| - | |**MODIFIED**|Only seen on REFRESH responses to indicate revalidation produced a new modified object.| | + | |**MODIFIED**|Only seen on **REFRESH** responses to indicate revalidation produced a new modified object.| |
| - | |**UNMODIFIED**|Only seen on REFRESH responses to indicate revalidation produced a 304 (Not Modified) status. The client gets either a full 200 (OK), a 304 (Not Modified), or (in theory) another response, depending on the client request and other details.| | + | |**UNMODIFIED**|Only seen on **REFRESH** responses to indicate revalidation produced a 304 (Not Modified) status. The client gets either a full 200 (OK), a 304 (Not Modified), or (in theory) another response, depending on the client request and other details.| |
| - | |**REDIRECT**|Squid generated an HTTP redirect response to this request. Only on Squid-3.2+ or Squid built with -DLOG_TCP_REDIRECTS compiler flag.| | + | |**REDIRECT**|Squid generated an HTTP redirect response to this request. Only on [[https:// |
| Line 37: | Line 37: | ||
| |**HIT**|The response object delivered was the local cache object.| | |**HIT**|The response object delivered was the local cache object.| | ||
| - | |**MEM**|Additional tag indicating the response object came from memory cache, avoiding disk accesses. Only seen on HIT responses.| | + | |**MEM**|Additional tag indicating the response object came from memory cache, avoiding disk accesses. Only seen on **HIT** responses.| |
| |**MISS**|The response object delivered was the network response object.| | |**MISS**|The response object delivered was the network response object.| | ||
| |**DENIED**|The request was denied by access controls.| | |**DENIED**|The request was denied by access controls.| | ||
| - | |**NOFETCH**|A ICP specific type. Indicating service is alive, but not to be used for this request. Sent during " | + | |**NOFETCH**|A ICP specific type. Indicating service is alive, but not to be used for this request. Sent during " |
| - | |**TUNNEL**|A binary tunnel was established for this transaction. Only on Squid-3.5+| | + | |**TUNNEL**|A binary tunnel was established for this transaction. Only on [[https:// |
| Line 48: | Line 48: | ||
| |**ABORTED**|The response was not completed due to the connection being aborted (usually by the client).| | |**ABORTED**|The response was not completed due to the connection being aborted (usually by the client).| | ||
| |**TIMEOUT**|The response was not completed due to a connection timeout.| | |**TIMEOUT**|The response was not completed due to a connection timeout.| | ||
| - | |**IGNORED**|While refreshing a previously cached response A, Squid got a response B that was older than A (as determined by the Date header field). Squid ignored response B (and attempted to use A instead). This " | + | |**IGNORED**|While refreshing a previously cached response A, Squid got a response B that was older than A (as determined by the Date header field). Squid ignored response B (and attempted to use A instead). This " |
| ---- | ---- | ||
pfsense/squid/squid_result_codes.1584287646.txt.gz · Last modified: 2020/07/15 09:30 (external edit)