Starting with tag: [TAG rfc2109-version-0.3.2 Alan-Shields@omrf.ouhsc.edu**20050921193537] [rfc2109: properly handle empty cookie strings (return nil) Alan-Shields@omrf.ouhsc.edu**20051216220746] [rfc2109: allow non-conformant paths, thanks to Richard Newman Alan Shields **20060127214239 Finally allow non-conformant paths. If the corrects-path-p option to cookie-string is nil, the library will not coerce the path to correctness. ] [Modernise rfc2109 defpackage form. rich at holygoat dot co uk**20060201070751] [Added missing fiveam dependency attila.lendvai@gmail.com**20060507004317] [FIX: empty strings are valid cookie values (they were quoted before) attila.lendvai@gmail.com**20060507004523] [Added missing fiveam dependency attila.lendvai@gmail.com*-20060507004317] [Disable fasl compilation in the asdf file attila.lendvai@gmail.com**20060626222923 This way we can get rid of the errors arising when rfc2109 is compiled with 5am loaded and later loaded from fasl without 5am loaded. ] [Created a rfc2109.test system attila.lendvai@gmail.com**20060627135446 Splitting the file into a main/test would have been a bad idea due to the smart inlining with the standard's text. The previous solution to always load the file is also bad for performance. The hopefully final solution is to create an rfc2109.test system and before loading rfc2109.lisp in it rebind *features* and push a symbol (:test) into it. The main lisp file #+test for this symbol and defines the tests when it's loaded through rfc2109.test. ] [easily strip RFC from rfc2109 for copyright concerns Alan Shields **20060809195818] [prevent error for short cookie strings marijnh@gmail.com**20060801102905] [add a test for the cookie-to-short bug Alan Shields **20060809201224] [rfc2109-version-0.4 Alan Shields **20060809201441] [update the changelog Alan Shields **20060809201515] [TAG rfc2109-version-0.4 Alan Shields **20060809201537] [Keep the order of cookies as they come attila.lendvai@gmail.com**20060901001540 This is important because if you have two cookies with the same name but with different paths then the more specific ones (based on the path) must be sooner in the list. ] [Call (length "$Version=") at read-time attila.lendvai@gmail.com**20060901001848] [Turn off corrects-path-p by default attila.lendvai@gmail.com**20060904095156 So, the situation is this: all the examples in the RFC use quotes around the path part, but the syntax description itself does not contain the quotes and IE gets confused by the extra (?) quotes, while FF works right with and without them. I think the entire corrects-path-p should be removed and the tests updated. ] [fix: max-age may be zero attila.lendvai@gmail.com**20080916223519]