[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: using find_token() for If-Match et al is bogus State-Changed-From-To: open-analyzed State-Changed-By: fielding State-Changed-When: Sun Sep 13 16:29:30 PDT 1998 State-Changed-Why: But, since we generate our own etags and know they do not contain any whitespace, it doesn't matter. Anything containing a space would never match one of our etags. It would be nice to have a find_value function that separated a field by the comma list items, removed extra whitespace, and then did a smart comparison.
