- tbnl-announce@common-lisp.net - mailman3.common-lisp.net

[hunchentoot-announce] New release 0.7.3
by Edi Weitz 28 Mar '07

28 Mar '07

ChangeLog: Version 0.7.3 2007-03-28 Added +HTTP-MULTI-STATUS+ Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, Edi.

1 0

[hunchentoot-announce] New release 0.7.2 (Was: Errors with test pages)
by Edi Weitz 09 Mar '07

09 Mar '07

And here's the next release. Sorry for the noise today. On Thu, 08 Mar 2007 21:22:48 +0900, Jong-won Choi <jc(a)itsec.co.kr> wrote: > Here is the backtrace. > > My example input for 'Enter a value:' is 日本語 Yes, there was a bug in the test suite which only affected LispWorks. I could only reproduce it because I had your example input to copy and paste from... :) The new release should fix that. Thanks for the bug report, Edi.

1 0

[hunchentoot-announce] New release 0.7.1 (Was: New release 0.7.0)
by Edi Weitz 09 Mar '07

09 Mar '07

On Fri, 9 Mar 2007 12:53:22 +0100, "Marko Kocić" <marko.kocic(a)gmail.com> wrote: > There's one more error in server.lisp 172-179 #-:hunchentoot-no-ssl > doesn't handle all parameters. Oh my, bad day today. Thanks for the heads-up, should be fixed now.

1 0

[hunchentoot-announce] New release 0.7.0 (Was: Hunchentoot sbcl :win32 patches)
by Edi Weitz 09 Mar '07

09 Mar '07

On Tue, 6 Mar 2007 10:44:42 +0100, "Marko Kocić" <marko.kocic(a)gmail.com> wrote: > I wanted to play with hunchentoot on widows using sbcl and made it > work (at least tests are working). In order to do so I had to > optinally disable ssl cause I couldn't find appropriate ssl library > to use. Also, I fixed issue with sbcl win32 port pushing :unix to > *features* and applied a patch from William Bland to work without > threads. Thanks. I've released a new version (haven't testet with SBCL/Win32, though) which incorportates your patches.

1 2

[hunchentoot-announce] New release 0.6.2 (Was: HTTP redirect bug in Allegro Lisp)
by Edi Weitz 22 Feb '07

22 Feb '07

On Wed, 21 Feb 2007 15:07:21 +0530, "Saurabh Nanda" <saurabhnanda(a)gmail.com> wrote: > I have a piece of code which runs in SBCL but is throwing an error > when running on Allegro Lisp. The relevant portion of the backtrace > thrown by hunchentoot is given below: > > ->(SYS::..RUNTIME-OPERATION . :UNKNOWN-ARGS) > (TPL:DO-COMMAND "zoom" :FROM-READ-EVAL-PRINT-LOOP NIL :COUNT T :ALL > T) > (TBNL:GET-BACKTRACE #1=#<SIMPLE-ERROR @ #x1001b57d32>) > ((:INTERNAL TBNL::PROCESS-REQUEST 0) #1#) > (SIGNAL #1#) > (ERROR SIMPLE-ERROR :FORMAT-CONTROL > "Attempt to store into purespace address #x~x." > :FORMAT-ARGUMENTS #2=(182935334912)) > (EXCL::ERROR-FROM-CODE 19 . #2#) > (SYS::..CONTEXT-SAVING-RUNTIME-OPERATION) (NSTRING-UPCASE #3="Location") > (TBNL::MAKE-KEYWORD #3#) > (TBNL:REDIRECT "http://URL-DELETED") > > In the make-keyword function. changing the default value of the > parameter destructivep to 'nil' solves this error. > > Is this a bug? Or what? Yes, that was clearly a bug - 0.6.2 fixes that. Thanks for the report, Edi.

1 0

[hunchentoot-announce] New release 0.6.1 (Was: Another error uploading file)
by Edi Weitz 24 Jan '07

24 Jan '07

On Wed, 24 Jan 2007 01:38:25 +0200, Ury Marshak <urym(a)two-bytes.com> wrote: > Although I seem to have stumbled on a different issue with > uploading. All it seems to take is to set the variable > *hunchentoot-default-external-format* to utf-8. Yes, this was already discussed a few days ago http://common-lisp.net/pipermail/tbnl-devel/2007-January/000983.html but I couldn't reproduce it. Your little test script was again very helpful in this case... :) I've now identified the error and just released a new version which should fix this. Thanks, Edi.

1 0

[hunchentoot-announce] New release 0.6.0 (Was: Error uploading file using mod_lisp2)
by Edi Weitz 23 Jan '07

23 Jan '07

On Mon, 22 Jan 2007 21:21:25 +0200, Ury Marshak <urym(a)two-bytes.com> wrote: > For testing I'm using a small python script that repeatedly uploads > the same file, it's available at > http://85.65.214.241/misc/test-upload.tar.gz Yes, I can reproduce the error. It seems (from my understanding of the RFCs) the error is actually in the Python code - it sends two CRLF sequences after the last content boundary where it should only send one. (Firefox, IE, and Drakma for example don't do that.) Anyway, I've tried to robustify Hunchentoot against erroneous client data like this. You should now only see a warning in the log file. I could upload 100 files in a row without problems using your test script. Also note that the new release now optionally accepts request bodies without a content length when behind mod_lisp2. You'll need Hugh Winkler's latest additions to mod_lisp2 for this. Cheers, Edi.

1 0

[hunchentoot-announce] New release 0.5.1
by Edi Weitz 18 Jan '07

18 Jan '07

ChangeLog: Version 0.5.1 2007-01-18 Even more flexible behaviour of RAW-POST-DATA Download: http://weitz.de/files/hunchentoot.tar.gz Sorry for the noise, Edi.

1 0

[hunchentoot-announce] New release 0.5.0
by Edi Weitz 17 Jan '07

17 Jan '07

ChangeLog: Version 0.5.0 2007-01-17 More flexible behaviour of RAW-POST-DATA Robustified PARSE-CONTENT-TYPE Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, Edi.

1 0

[hunchentoot-announce] New release 0.4.14
by Edi Weitz 17 Jan '07

17 Jan '07

Changelog: Version 0.4.14 2007-01-17 More meaningful results for RAW-POST-DATA Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, Edi.

1 0