Unknown methods, how to handle.

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Mon, 03 May 1999 23:08:28 +0200

HTTP defines method as an extensible set of commands, and proxies are
required to pass throught any methods it does not understand, and to
expunge any cached objects on that URI when doing so.

Any ideas on how we could handle this in a somewhat clean manner?

Also, it may effect digests, as HTTP method is included in the digest
key.

My ideas:
* When receiving a request, store method verbatim as a string, and
decode those methods Squid needs to take special actions on. Other
methods decoded as UNKNOWN or OTHER.
* When sending a request, use the string, not the encoded value.
* Logging should also use the string from obvious reasons, with
appropriate encoding to filter out "bad" characters from the log.
* For digests, use the string representation, not a encoded integer
value, or define digest to be valid only for certain well defined
methods or classes of objects (full object, partial object, headers
only).

/Henrik
Received on Tue Jul 29 2003 - 13:15:58 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:12:07 MST