Commit a31b8a93 authored by Alan Shields's avatar Alan Shields
Browse files

update the changelog

darcs-hash:cbe018d38a198bb5f10b0d0a8a5756a066e5f4b4
parent b1bbebe3
Loading
Loading
Loading
Loading
+86 −1
Original line number Original line Diff line number Diff line
Wed Aug 10 17:28:08 CDT 2005  Alan-Shields@omrf.ouhsc.edu
Wed Aug  9 15:14:41 CDT 2006  Alan Shields <patches@alan.shields.name>
  * rfc2109-version-0.4

Wed Aug  9 15:12:24 CDT 2006  Alan Shields <patches@alan.shields.name>
  * add a test for the cookie-to-short bug

Tue Aug  1 05:29:05 CDT 2006  marijnh@gmail.com
  * prevent error for short cookie strings

Wed Aug  9 14:58:18 CDT 2006  Alan Shields <patches@alan.shields.name>
  * easily strip RFC from rfc2109 for copyright concerns

Tue Jun 27 08:54:46 CDT 2006  attila.lendvai@gmail.com
  * Created a rfc2109.test system
  
  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.

Mon Jun 26 17:29:23 CDT 2006  attila.lendvai@gmail.com
  * Disable fasl compilation in the asdf file
  
  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.

Sat May  6 19:43:17 CDT 2006  attila.lendvai@gmail.com
  UNDO: Added missing fiveam dependency

Sat May  6 19:45:23 CDT 2006  attila.lendvai@gmail.com
  * FIX: empty strings are valid cookie values (they were quoted before)

Sat May  6 19:43:17 CDT 2006  attila.lendvai@gmail.com
  * Added missing fiveam dependency

Wed Feb  1 01:07:51 CST 2006  rich at holygoat dot co uk
  * Modernise rfc2109 defpackage form.

Fri Jan 27 15:42:39 CST 2006  Alan Shields <Alan-Shields@omrf.ouhsc.edu>
  * rfc2109: allow non-conformant paths, thanks to Richard Newman
  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.

Fri Dec 16 16:07:46 CST 2005  Alan-Shields@omrf.ouhsc.edu
  * rfc2109: properly handle empty cookie strings (return nil)

Wed Sep 21 14:35:37 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  tagged rfc2109-version-0.3.2

Tue Sep 20 16:22:50 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  * rfc2109: allow nil to be passed to safe-parse-cookies
  The docs say that you can pass nil to safe-parse-cookies to have no
  legal domains to allow cookies to come from (ie they must come from your
  server or not at all).
  Whoops.

Thu Aug 25 15:26:18 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  tagged rfc2109-version-0.3.1

Thu Aug 25 15:06:51 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  * rfc2109 - Marco applied the 5am patch, changed keyword
  Marco wanted the feature keyword to be 5am. Less typing for me!

Thu Aug 25 11:59:56 CDT 2005  rich@holygoat.co.uk
  * Ensure that input to destructuring-bind in parse-cookies-vnetscape is a 2-element list.

Thu Aug 11 17:18:15 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  * rfc2109: Add basic testing and a tester
  Decided to add a basic testing framework - mostly because I'm mucking about
  with parsing and another library, want something to let me know when I've
  REALLY screwed up.
  
  Please note that the current stable version of FiveAM will not run these tests,
  as it doesn't have the *features* that are needed to define them. I've submitted
  a patch to Marco, we'll see if he adds it.

Wed Aug 10 17:31:25 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  tagged rfc2109-version-0.3
  tagged rfc2109-version-0.3


Wed Aug 10 17:31:01 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  * rfc2109: update changelog for release

Wed Aug 10 17:27:25 CDT 2005  Alan-Shields@omrf.ouhsc.edu
Wed Aug 10 17:27:25 CDT 2005  Alan-Shields@omrf.ouhsc.edu
  * rfc2109: update version number for release
  * rfc2109: update version number for release
  Don't really know how I missed updating the version number for 0.2 and 0.2.1...
  Don't really know how I missed updating the version number for 0.2 and 0.2.1...