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

[hunchentoot-devel] (Non)-Bug in subclassing dav:file-resource
by Ralf Mattes 23 May '07

23 May '07

Ok, I looked closer at the code for authorized-file-resource - I forgot to implement accept-request-p ... after fixing this everything works fine now. Thanks, RalfD

2 1

[hunchentoot-devel] problem on macosx with openmcl
by syamajala＠gamebox.net 23 May '07

23 May '07

Hello, I have been trying to get hunchentoot to work on mac os x with openmcl. It seems to load correctly and everything, but when I compile my program and try to access the page i get an error that says: Unknown http return code: 500 - Seshu

2 1

[hunchentoot-devel] Bugreport (and patch)
by Ralf Mattes 20 May '07

20 May '07

Hello, during some moderate WebDAV conformance tests is stumbled over the following bug/typo: --- handlers.lisp 2007-04-18 02:29:07.000000000 +0200 +++ /LISP/ediware/cl-webdav/handlers.lisp 2007-05-19 17:05:45.000000000 +0200 @@ -314,7 +314,7 @@ (let ((resource (get-resource))) (when (resource-exists resource) (setf (header-out :allow) - (format nil "~{~A~^~, ~}" + (format nil "~{~A~^, ~}" (set-difference *allowed-methods* '(:get :head :mkcol)))) (method-not-allowed)) (let ((parent (resource-parent resource))) MKCOL on an existing resource created an 500 status instead of the expected 405. Cheers, RalfD

2 3

[hunchentoot-devel] Logging with cronolog (hunchentoot behind mod_proxy)
by Andrei Stebakov 20 May '07

20 May '07

I am wondering if anyone is using cronolog with hunchentoot to split logging by year, month and day? I am using hunchentoot behind mod_proxy so can I rely on Apache's settings like CustomLog "|/usr/bin/cronolog /WebLogs/%Y/%m/%d-access.log".? I am just looking for some ideas how you split the log. Thank you, Andrew

1 0

[hunchentoot-devel] per server easy-handler-alist
by Mac Chan 18 May '07

18 May '07

Since Edit added the ultra-flexible macro define-easy-handler, I have replaced all my custom dispatch functions with it. There's a small issue with this macro, since it modifies the global *easy-handler-alist*. In production I have two server instances, one http and one https. I cannot easily say, for example, I want the following apply only to the https server instance. (define-easy-handler (home-page :uri "/login") () (with-html ...)) (define-easy-handler (home-page :uri "/my-account") () (with-html ...)) The problem is that start-server happens at run-time but define-easy-handler happens at load-time, so you cannot associate any server specific binding in define-easy-handler. Attached is a patch that introduce a slot :name to the server class and a global variable *servers* which is an a-list mapping names to server instances. With this you can do something like (define-easy-handler (home-page :uri "/hunchentoot/test/easy-home.html" :server-names '(:http)) () (with-html (:html (:body "Home page")))) (define-easy-handler (login-page :uri "/hunchentoot/test/easy-login.html" :server-names '(:https)) () (with-html (:html (:body "Secure login")))) (define-easy-handler (common-page :uri "/hunchentoot/test/easy-common.html" :server-names '(:https :http)) () (with-html (:html (:body "Common page")))) (start-server :name :http :port 8000) (stop-server :http) (start-server :name :https :port 4443) (stop-server :https) If you are not using multiple servers, this change will be transparent. I'd appreciate any suggestions. Regards, -- Mac

2 2

[hunchentoot-devel] ACL case sensitive reader incompatibilities
by Vyacheslav Akhmechet 16 May '07

16 May '07

I seem to run into some issues with Hunchentoot on ACL due to case sensitivity. When I turn case sensitivity off using '(set-case-mode :case-insensitive-upper)', everything behaves as expected. However, when I run in ACL's default mode, some things don't seem to work. Here is a list of issues I run into without the case-mode fix: 1. Loading Hunchentoot with asdf throws me into a debugger saying I need a newer version of TRIVIAL-GRAY-STREAMS. If I choose to continue at this point, I get another error in the debugger saying "Package :flexi-streams does not exist." When I choose an option to create it anyway, Hunchentoot loads fine. 2. (request-method) function returns symbols in the "incorrect" case - :GET and :POST, intead of :get and :post. This means it's not possible to simply compare symbols (using ecase, for example) - it becomes necessary to compare their names (with a case insensitive string comparison). Franz gives guidelines on how to write software that runs both on case sensitive and case insensitive implementations here: http://www.franz.com/support/documentation/5.0.1/doc/cl/case.htm. Are these being used by Hunchentoot? 3. Sessions/parameters don't seem to work properly. URL rewriting works, however it looks like the cookie functionality does not work. Additionally, (post-parameters) always returns nil on POST requests - effectively it's only possible to operate in GET mode. I'm not sure if Hunchentoot is meant to support ACL in its default reader mode, so I thought I'd report these issues. Regards, - Slava Akhmechet

2 1

[hunchentoot-devel] A typo in Hunchentoot doc?
by Victor Kryukov 16 May '07

16 May '07

Fourth paragraph of define-easy-handler documentation reads: The resulting handler will be a Lisp function with the name name and keyword parameters named by the var symbols. Each var will be bound to the value of the GET or POST parameter called real-name (a string) before the body of the function is executed. If real-name is not provided, it will be computed by downcasing the symbol name of name. It seems to me that last 'name' should be replace by 'var'. Regards, Victor. -- Yours Sincerely, Victor Kryukov

5 6

[hunchentoot-devel] *catch-errors-p* and spurious stream errors patch (add your own implementation and shake).
by Vladimir Sedach 11 May '07

11 May '07

Hello, While debugging a web application, the need to not catch errors became apparent. Unfortunately, there are spurious stream errors that make this less than useful currently (someone has informed me that this problem is well known). The attached patch is my proposal to let people deal with this and take advantage of (setf *catch-errors-p* nil). If you think this is the wrong way of going about things, please let me know. Thanks, Vladimir

3 6

[hunchentoot-devel] Can't write to FD-STREAM: Broken pipe
by Slava Akhmechet 11 May '07

11 May '07

I'm looking through the Hunchetoot log and occassionally I see the following messages: [2007-05-11 14:50:37 [ERROR]] Error while processing connection: couldn't write to #<SB-SYS:FD-STREAM for "a constant string" {BA242B1}>: Connection reset by peer [2007-05-11 14:50:37 [ERROR]] Error while processing connection: couldn't write to #<SB-SYS:FD-STREAM for "a constant string" {BDF02B1}>: Broken pipe I don't see any problems in the browser, I only found out about these messages because I looked at the log. Can someone think of a situation in which these errors would occur without interrupting user experience and why? -- Regards, Slava Akhmechet.

2 1

[hunchentoot-devel] HTTP PUT and DELETE
by Tiarnan O'Corrain 11 May '07

11 May '07

Hi-- does Hunchentoot support these, and if not, would it take much effort to implement them? Anyone else interested? regards Tiarnán

3 2