May 2008 - tbnl-devel@common-lisp.net - mailman3.common-lisp.net

[hunchentoot-devel] Current development
by Edi Weitz 14 Jun '08

14 Jun '08

As common-lisp.net has been pretty unreliable in the last days, we've moved development over to the bknr.net server maintained by Hans. If you're interested in trying out the soon-to-be-released Hunchentoot version, get all of Hunchentoot, Chunga, and FLEXI-STREAMS from here: http://bknr.net/trac/browser/trunk/thirdparty If you're using Drakma, you'll have to grab it from bknr.net as well, as there are incompatible changes in Chunga. The previous development history can be seen at http://trac.common-lisp.net/tbnl/browser/branches whenever the server is up. Edi.

9 29

[hunchentoot-devel] hunchentoot-error error
by Cyrus Harmon 31 May '08

31 May '08

conditions.lisp has two definitions of hunchentoot-error, and none for hunchentoot-warn. the following patch fixes this: Index: conditions.lisp =================================================================== --- conditions.lisp (revision 3232) +++ conditions.lisp (working copy) @@ -1,5 +1,5 @@ -;;; -*- Mode: LISP; Syntax: COMMON-LISP; Package: ODD-STREAMS; Base: 10 -*- -;;; $Header: /usr/local/cvsrep/odd-streams/conditions.lisp,v 1.5 2007/12/31 01:08:45 edi Exp $ +;;; -*- Mode: LISP; Syntax: COMMON-LISP; Package: HUNCHENTOOT; Base: 10 -*- +;;; $Header: /usr/local/cvsrep/hunchentoot/conditions.lisp,v 1.5 2007/12/31 01:08:45 edi Exp $ ;;; Copyright (c) 2008, Dr. Edmund Weitz. All rights reserved. @@ -56,7 +56,7 @@ () (:documentation "Like HUNCHENTOOT-WARNING but with formatting capabilities.")) -(defun hunchentoot-error (format-control &rest format-arguments) +(defun hunchentoot-warn (format-control &rest format-arguments) "Signals a warning of type HUNCHENTOOT-SIMPLE-WARNING with the provided format control and arguments." (warn 'hunchentoot-simple-warning

2 1

[hunchentoot-devel] New release 0.15.7 (and also FLEXI-STREAMS 0.15.0)
by Edi Weitz 31 May '08

31 May '08

This is a tiny change which should improve Hunchentoot's performance. Incidentally, if you're concerned about performance, you might consider giving FLEXI-STREAMS 0.15.0 a try which was also released today. http://weitz.de/files/hunchentoot.tar.gz http://weitz.de/files/flexi-streams.tar.gz I'd also recommend to everyone interested in Hunchentoot's future directions to check out Hans' current version from here http://trac.common-lisp.net/tbnl/browser/branches/hans and to play with it. This version needs an updated Chunga (at least 0.4.2): http://weitz.de/files/chunga.tar.gz Edi.

2 1

[hunchentoot-devel] conditional reader error
by Cyrus Harmon 31 May '08

31 May '08

In hunchentoot.asd, I think the #+(not foo bar ...) bit is wrong: Index: hunchentoot.asd =================================================================== --- hunchentoot.asd (revision 3230) +++ hunchentoot.asd (working copy) @@ -76,7 +76,7 @@ #+(and :lispworks :unix) (:file "unix-lw") #+(and :openmcl :unix) (:file "unix-mcl") #+(and :sbcl :unix (not :win32)) (:file "unix-sbcl") - #+(and (not :allegro :clisp :cmu :lispworks :openmcl :sbcl) :unix) (:file "unix-other") + #+(and (not (or :allegro :clisp :cmu :lispworks :openmcl :sbcl)) :unix) (:file "unix-other") (:file "set-timeouts") (:file "connection-manager") (:file "server")

2 1

[hunchentoot-devel] Handling multiple Hunchentoot instances with potentially conflicting ports
by Raditya Kertiyasa 30 May '08

30 May '08

Hi everbody, I'm a Lisp newbie but I need to get my system up and running fast. I'm building a system that might cause multiple Hunchentoot servers to use conflicting ports. I want to handle this with an error handler and I've setup a wrapper function to start Hunchentoot and a restart function: ;; restart function to handle conflicting ports (defun ht-port-conflict-handler (condition) (... do something here to address the conflicting ports ...) (invoke-restart 'ht-port-conflict-handler)) ;; Start Hunchentoot Server with error-handling (defun ht-start-with-error-handler () (handler-bind ((simple-error #'ht-port-conflict-handler)) (restart-case (setf *ht-handle* (hunchentoot:start-server :port *ht-port*)) (ht-port-conflict-handler () nil)))) The system should allow users to reconfigure their instance of Hunchentoot without having to invoke the debugger, but when I run this code I always end up in the debugger anyway. Can anybody tell me where I went wrong? Or maybe there's a better solution for my situation? Regards, Raditya Kertiyasa

3 11

[hunchentoot-devel] as-keyword and other utility functions
by Cyrus Harmon 30 May '08

30 May '08

I see that in some of my code I was relying on hunchentoot::make- keyword, which has now gone away. But there is as-keyword and there is chunga::make-keyword. And there's, of course, alexandria:make-keyword, if I want to use that. It's a trivial function, but would it make sense to take things like with-unique-names, make-keyword, etc... and put it in some sort of ediware-utilities package? It's a trivial issue in this case, but I figured I'd bring it up for handy and less-trivial things like with-rebinding, etc... thanks, Cyrus

2 3

[hunchentoot-devel] Using multiple Hunchentoot-Requests in one thread
by css 29 May '08

29 May '08

Hello. My problem may seem strange, but: I have a huge download to generate on my hunchentoot, and I dont want to have one thread for each of these downloads, but one thread answering multiple requests at the same time (since the generation takes time, caching takes space, and sending the generated code to multiple receivers seems the best idea to me). That is, I want to get the request-object, and then pass it to another thread, who is then handling multiple requests (i.e. sending "non-waiting", polling for input, etc.). Is this possible?

5 12

[hunchentoot-devel] Encoding issues in auhtorization header
by Christian Haselbach 22 May '08

22 May '08

Hello, I just stumbled upon an encoding problem with the authorization header. It cannot really handle UTF-8 encoded user names (or passwords), because base64:base64-string-to-string does not respect the used encoding. In my local instance, I fixed this by changing hunchentoot's authorization function as follows: (defun authorization (&optional (request *request*)) "Returns as two values the user and password \(if any) as encoded in the 'AUTHORIZATION' header. Returns NIL if there is no such header." (let* ((authorization (header-in :authorization request)) (start (and authorization (> (length authorization) 5) (string-equal "Basic" authorization :end2 5) (scan "\\S" authorization :start 5)))) (when start (let* ((auth-octets (base64:base64-string-to-usb8-array (subseq authorization start))) (auth (octets-to-string auth-octets :external-format *hunchentoot-default-external-format*))) (destructuring-bind (&optional user password) (split ":" auth) (values user password)))))) Or as patch: 286,288c286,293 < (destructuring-bind (&optional user password) < (split ":" (base64:base64-string-to-string (subseq authorization start))) < (values user password))))) --- > (let* ((auth-octets (base64:base64-string-to-usb8-array > (subseq authorization start))) > (auth (octets-to-string auth-octets > :external-format > *hunchentoot-default-external-format*))) > (destructuring-bind (&optional user password) > (split ":" auth) > (values user password)))))) Regards, Christian

3 9

Re: [hunchentoot-devel] hunchentoot + nginx
by Anton Vodonosov 22 May '08

22 May '08

Hi, Nick. I'm using hunchentoot behind nginx, but not to say I've learned any lessons. It works (why not?). Good luck, -Anton 19.05.08, 19:41, "Nick Allen" : >is anyone out there using hunchentoot behind nginx? > >if so would they be willing to post any pointers / experiences / lessons learned / reasons not to? > >take care > >Nick

2 1

[hunchentoot-devel] hunchentoot + nginx
by Nick Allen 19 May '08

19 May '08

is anyone out there using hunchentoot behind nginx? if so would they be willing to post any pointers / experiences / lessons learned / reasons not to? take care Nick

1 0