21.7. Metodi di richiesta supportati

Squid riconosce diversi metodi di richiesta HTTP che vengono definiti nella RFC 2616 (http://www.w3.org/Protocols/rfc2616/rfc2616.html) - Hypertext Transfer Protocol -- HTTP/1.1. Le nuove versioni di Squid, in particolare a partire da squid-2.2.STABLE5 e versioni successive, riconoscono anche i metodi di richiesta che sono descritti nella RFC 2518 (http://www.faqs.org/rfcs/rfc2518.html) - HTTP Extensions for Distributed Authoring -- WEBDAV. La lista che alleghiamo di seguito è disponibile alla URLs http://www.squid-cache.org/Doc/FAQ/FAQ-6.html#ss6.9

method    defined    cachabil meaning
--------- ---------- ---------- ----------------------------------
GET       HTTP/0.9   possibly object retrieval and simple searches
HEAD      HTTP/1.0   possibly metadata retrieval
POST      HTTP/1.0   CC or Exp. submit data (to a program)
PUT       HTTP/1.1   never upload data (e.g. to a file)
DELETE    HTTP/1.1   never remove resource (e.g. file)
TRACE     HTTP/1.1   never appl. layer trace of request route
OPTIONS   HTTP/1.1   never request available comm. options
CONNECT   HTTP/1.1r3 never tunnel SSL connection
ICP_QUERY            Squid never used for ICP based exchanges
PURGE                Squid never remove object from cache
PROPFIND  rfc2518    ? retrieve properties of an object
PROPATCH  rfc2518    ? change properties of an object
MKCOL     rfc2518    never create a new collection
COPY      rfc2518    never create a duplicate of src in dst
MOVE      rfc2518    never atomically move src to dst
LOCK      rfc2518    never lock an object against modifications
UNLOCK    rfc2518    never unlock an object