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

Re: [Fwd: [hunchentoot-devel] Having trouble withcreate-folder-dispatcher-and-handler]
by Cunningham, Jeff 17 Dec '07

17 Dec '07

Hans Hübner wrote: > The change to enough-url modifies it so that it behaves the same as > enough-namestring (which was previously used) does. What I am not > sure about is whether the create-folder-dispatcher-and-handler > dispatcher and handler can handle an empty path. What you'd propably > want to see is a directory listing? Can you fetch files if you > specify the complete URL? > > -Hans > > Yes, I can fetch files with a complete URL. And you are right - I'd like to see a directory listing. I just re-ran hunchentoot-test. With this url I get the image file: http://localhost:3001/hunchentoot/code/fz.jpg But with this URL I get a 400: bad request http://localhost:3001/hunchentoot/code/ --Jeff

2 1

[Fwd: [hunchentoot-devel] Having trouble with create-folder-dispatcher-and-handler]
by Cunningham, Jeff 17 Dec '07

17 Dec '07

> Can you please try with the attached patch? > > Thanks, > Hans > /> />

2 1

[hunchentoot-devel] Having trouble with create-folder-dispatcher-and-handler
by Jeff Cunningham 17 Dec '07

17 Dec '07

I haven't used this handler for awhile, but I do recall it worked the last time I did. Now, when I set up a simple test case it fails, generating an Internal Server Error (500) with this error message in the log: [error] [Hunchentoot] The value NIL is not of type (MOD 536870911) I isolated it as far as the enough-url function, where it seems that the mismatch is returning NIL and the subseq doesn't like it. My test case is: (create-folder-dispatcher-and-handler "/test/" #p"/home/hunchentoot/test/" "text/plain") Both folders exist and are world readable. I am running SBCL 1.0.12. I tried checking what the arguments are to enough-url when it fails - they are: "url=/test/ url-prefix=/test/ which, of course, explains the NIL and the failure of the subseq. I don't understand how this handler is supposed to work, which it makes it difficult for me to troubleshoot further. Any idea why this doesn't work? --Jeff

2 1

[hunchentoot-devel] Google search result
by Bob Hutchison 15 Dec '07

15 Dec '07

Hi Edi, Debating whether to mention this or not... Have you noticed the text that shows up when you search for Hunchentoot in google: "HUNCHENTOOT - The Common Lisp web server formerly known as TBNL Web server coded in Common Lisp; supports HTTP/1.1 chunking, persistent connections (keep-alive), and SSL; works only with LispWorks." The 'works only with LispWorks' bit is maybe something you don't want there? Cheers, Bob ---- Bob Hutchison -- tumblelog at http://www.recursive.ca/so/ Recursive Design Inc. -- weblog at http://www.recursive.ca/hutch http://www.recursive.ca/ -- works on http://www.raconteur.info/cms-for-static-content/home/

4 8

[hunchentoot-devel] how to diagnose output problem?
by Jim Prewett 07 Dec '07

07 Dec '07

Hello, I'm new to Hunchentoot. :) I'm working on an app that uses the Demo Allegro Lisp, the AGraph package, and Hunchentoot for the front-end. When I run on MacOS, everything seems great! When I run on Linux, things are not so good. I get *NO* output from Hunchentoot when I put certain records into the database. I don't have any idea if this is a Hunchentoot bug, a Agraph/Franz bug, or a bug in my understanding :) I don't see any errors at the REPL - I've not hit the limitations of the demo ACL. The function I use, when I put (warn ...) statements in, clearly finds all of the records I've requested and thinks its done all of its work (it believes its output the entire webpage), but I get no output :P Can anyone give me suggestions on how to tell /where/ I'm having the problem? I got hunchentoot and friends from asdf-install this morning on both systems (Mac and Linux). I'm running the latest ACL/AGraph. I've set *SHOW-LISP-BACKTRACES-P* and *SHOW-LISP-ERRORS-P* to t and don't see any errors. Here is a transcript of using telnet to request the page: # telnet localhost 80 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. GET /list?user=download HTTP/1.1 200 OK Content-Type: text/html; charset=iso-8859-1 Date: Thu, 06 Dec 2007 15:41:26 GMT Server: Hunchentoot 0.14.7 Connection: Close Set-Cookie: hunchentoot-session=7%3a355b027548e5bd694b3dd0b7b477b018; path=/ Connection closed by foreign host. Thanks for any ideas, Jim James E. Prewett Jim(a)Prewett.org download(a)hpc.unm.edu Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/ Designated Security Officer OpenPGP key: pub 1024D/31816D93 HPC Systems Engineer III UNM HPC 505.277.8210

5 8

[hunchentoot-devel] Problem with flexi-stream-bound on openmcl
by Denis Mashkevich 05 Dec '07

05 Dec '07

Hello, I have a problem running hunchentoot on openmcl (OpenMCL Version 1.1-pre-070512 (DarwinPPC32), hunchentoot 0.14.2, flexi-streams 0.13.0) The error is: Undefined function SETF::|HUNCHENTOOT::FLEXI-STREAM-BOUND| called with arguments (NIL #<FLEXI-STREAMS::FLEXI-LATIN-1-IO-STREAM #x92CD646>) . The error is signaled on every request. Doing this as a way of test from REPL seems to be working ok: TBNL> (make-instance 'flex::flexi-latin-1-io-stream ) #<FLEXI-STREAMS::FLEXI-LATIN-1-IO-STREAM #x9374906> TBNL> (setf (flexi-stream-bound *) nil) NIL TBNL> (symbol-package 'flexi-stream-bound) #<Package "FLEXI-STREAMS"> Under lispworks it runs ok on the same system. Backtrace follows: Undefined function SETF::|HUNCHENTOOT::FLEXI-STREAM-BOUND| called with arguments (NIL #<FLEXI-STREAMS::FLEXI-LATIN-1-IO-STREAM #x92CD646>) . [Condition of type CCL::UNDEFINED-FUNCTION-CALL] Restarts: 0: [CONTINUE] Retry applying SETF::|HUNCHENTOOT::FLEXI-STREAM-BOUND| to (NIL #<FLEXI-STREAMS::FLEXI-LATIN-1-IO-STREAM #x92CD646>). 1: [USE-VALUE] Apply specified function to (NIL #<FLEXI- STREAMS::FLEXI-LATIN-1-IO-STREAM #x92CD646>) this time. 2: [STORE-VALUE] Specify a function to use as the definition of SETF::|HUNCHENTOOT::FLEXI-STREAM-BOUND|. 3: [ABORT-BREAK] Reset this process 4: [ABORT] Kill this process Backtrace: 0: (#<Anonymous Function #x85ED03E> 0 20) 1: (SWANK:BACKTRACE 1 41) 2: (CCL::CALL-CHECK-REGS 'SWANK:BACKTRACE) 3: (#<Anonymous Function #x861931E> '(SWANK:BACKTRACE 1 41) 36 'NIL) 4: (#<Anonymous Function #x8574DE6> #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x863212E> #<COMPILED-LEXICAL-CLOSURE #x92E6D86>) 5: (FUNCALL 'SWANK::EVAL-FOR-EMACS) 6: (SWANK::SLDB-LOOP #<CONNECTION #x8656776>) 7: (SWANK::CALL-WITH-BINDINGS '((*PRINT-PRETTY* . T) (*PRINT- LEVEL* . 4) (*PRINT-LENGTH* . 10) (*PRINT-CIRCLE* . T) (*PRINT-READABLY*) (*PRINT-PPRINT-DISPATCH* . #S(CCL::PPRINT-DISPATCH-TABLE :CONSES-WITH-CARS #<HASH- TABLE :TEST EQ size 60/60 #x85FEDAE> :STRUCTURES NIL :OTHERS (# #))) (*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*) (*PRINT-ARRAY* . T) ...) #<Anonymous Function #x8631096>) 8: (#<Anonymous Function #x85EDEF6> #<Anonymous Function #x86310E6>) 9: (SWANK::DEBUG-IN-EMACS #<CCL::UNDEFINED-FUNCTION-CALL #x92CCB66>) 10: (#<Anonymous Function #x8574DE6> #<Compiled-function SWANK:SWANK- DEBUGGER-HOOK #x863212E> #<COMPILED-LEXICAL-CLOSURE #x92CC4C6>) 11: (SWANK::CALL-WITH-REDIRECTED-IO #<COMPILED-LEXICAL-CLOSURE #x92CC4AE> #<Compiled-function SWANK:SWANK-DEBUGGER-HOOK #x863212E>) 12: (SWANK::CALL-WITH-CONNECTION #<CONNECTION #x8656776> #<COMPILED- LEXICAL-CLOSURE #x92CC4C6>) 13: (INVOKE-DEBUGGER #<CCL::UNDEFINED-FUNCTION-CALL #x92CCB66>) 14: (SIGNAL #<CCL::UNDEFINED-FUNCTION-CALL #x92CCB66>) 15: (CCL::%ERROR 'NIL #<CCL::FAKE-STACK-FRAME #x233AAE6>) 16: (CCL::DEFAULT-UNDEFINED-FUNCTION-CALL-RESTARTS #<CCL::FAKE-STACK- FRAME #x233AAE6> #<A Foreign Pointer [stack-allocated] #xF0734B40> 'SETF::|CCL::XP-GPR-LISP|) 17: (CCL::HANDLE-UDF-CALL #<CCL::FAKE-STACK-FRAME #x233AAE6> 'CCL::% ERROR) 18: (#<Anonymous Function #x8216916> 67108868 'NIL '(NIL) 'CCL::%ERR- DISP-INTERNAL #<CCL::FAKE-STACK-FRAME #x233AAE6> 2 0 #<A Foreign Pointer [stack-allocated] #xF0734B40>) 19: (CCL::FUNCALL-WITH-ERROR-REENTRY-DETECTION #<COMPILED-LEXICAL- CLOSURE #x233AAA6>) 20: (#<Anonymous Function #x821699E> 67108868 'NIL '(NIL) 'CCL::%ERR- DISP-INTERNAL 2 0 #<A Foreign Pointer [stack-allocated] #xF0734B40> #<CCL::FAKE-STACK-FRAME #x233AAE6>) 21: (CCL::FUNCALL-WITH-XP-STACK-FRAMES 0 0 0) 22: (CCL::%XERR-DISP -65220390) 23: (CCL::%PASCAL-FUNCTIONS% 2 -65220390) 24: (HUNCHENTOOT::PROCESS-CONNECTION #<HUNCHENTOOT::SERVER #x928A32E> #<BASIC-TCP-STREAM ISO-8859-1 (SOCKET/12) #x92BF386>) 25: (CCL::RUN-PROCESS-INITIAL-FORM '(#<COMPILED-LEXICAL-CLOSURE #x92BEA66>) #<PROCESS hunchentoot-worker-1(9) [Active] #x92BEB0E>) 26: (#<Anonymous Function #x8174C16> '(#<COMPILED-LEXICAL-CLOSURE #x92BEA66>) 0) 27: (#<Anonymous Function #x815EF56> 788848 #<LISP-THREAD hunchentoot- worker-1 [tcr @ #x3025C0] #x92BED5E>)

3 7

[hunchentoot-devel] Re: Hunchentoot's query parameter seperator
by Edi Weitz 01 Dec '07

01 Dec '07

Hi, On Tue, 20 Nov 2007 09:31:01 -0500, "Kyle R. Burton" <kyle.burton(a)gmail.com> wrote: > I'm not sure if there is a mailing list that would be more > appropriate. Really? http://weitz.de/hunchentoot/#mail I'd appreciate if we could continue this discussion on the list, see Cc. (You have to subscribe first, of course.) > I'd like to start by saying thanks for Hunchentoot! (and all the > other CL libraries you've developed). You're welcome... :) > I am just starting with Hunchentoot, but I noticed that the query > string parser supports ampersand (&) as a pair separator and I > rememberd semi-colon (;) also being a valid separator for query > strings. I only remember this from having worked with Perl's CGI. > A bit of quick searching on the net lead me to: > > http://en.wikipedia.org/wiki/Query_string > http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2 > > to confirm that the semi-colon is mentioned as a separator. I have to admit that this is the first time I've heard of this recommendation. A quick test with the vastly popular PHP shows that they don't implement it either: <? print_r($_GET); ?> Try these: http://zappa.agharta.de/test.html?foo=bar&baz=quux http://zappa.agharta.de/test.html?foo=bar;baz=quux So, to everyone on the list - what's your experience with semicolons as query string separators? Is this normal or esoteric? And, even more interesting, does any client out there actually use this convention? > I looked into the sources and I think the minor change is in > defmethod initialize-instance :after, to just update the split from: > > (form-url-encoded-list-to-alist (split "&" query-string)) > > to > > (form-url-encoded-list-to-alist (split "[;&]" query-string)) > > A quick empirical test with a browser shows symptoms of working: > > /lisp/test?foo=bar&qux=baz&blarf=qbozzle > /lisp/test?foo=bar;qux=baz;blarf=qbozzle > > I'm new to CL so I'm not entirely confident of my suggestion... Seems OK, but it might break existing applications. > Also, is there a place in the source tree for any kind of unit tests > or assertions? I'd have added one for this test, but I didn't > recognize where it would have been appropriate to put it. No, only the demo in the "test/" directory. > Is this something you'd consider enhancing Hunchentoot with? Lots of stuff... Cheers, Edi.

5 7

[hunchentoot-devel] Hunchentoot on abcl?
by Tiarnan O'Corrain 28 Nov '07

28 Nov '07

Hi-- I'm trying to get hunchentoot running on abcl, but it is balking at cffi. Does Hunchentoot use CFFI even when SSL is disabled? Should CFFI be compiled when :hunchentoot-no-ssl is on features? CL-USER(4): (asdf:oos 'asdf:load-op 'hunchentoot) ; loading system definition from /home/ocorrait/systems/hunchentoot.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :HUNCHENTOOT {847C91}> as HUNCHENTOOT ; loading system definition from /home/ocorrait/systems/url-rewrite.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :URL-REWRITE {C115}> as URL-REWRITE ; loading system definition from /home/ocorrait/systems/rfc2388.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :RFC2388 {122F17B}> as RFC2388 ; loading system definition from /home/ocorrait/systems/md5.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM MD5 {10E6817}> as MD5 ; loading system definition from /home/ocorrait/systems/cl+ssl.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :CL+SSL {C0DC01}> as CL+SSL ; loading system definition from /home/ocorrait/systems/flexi-streams.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :FLEXI-STREAMS {D1FA4}> as FLEXI-STREAMS ; loading system definition from /home/ocorrait/systems/trivial-gray-streams.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :TRIVIAL-GRAY-STREAMS {3F1F39}> as TRIVIAL-GRAY-STREAMS ; loading system definition from /home/ocorrait/systems/cffi.asd into #<PACKAGE "ASDF0"> Error loading /nfs/ck/home/ocorrait/site/cffi_0.9.2/cffi.asd at line 30 (offset 1412) Debugger invoked on condition of type SIMPLE-ERROR: Sorry, this Lisp is not yet supported. Patches welcome! Restarts: 0: TOP-LEVEL Return to top level. [1] ASDF0(5): 0 CL-USER(6): *features* (:ASDF :HUNCHENTOOT-NO-SSL :JAVA-1.4 :ARMEDBEAR :ABCL :COMMON-LISP :ANSI-CL :UNIX :SUNOS) regards tiarnán

2 1

[hunchentoot-devel] printing to *standard-output* in a multithreaded environment
by Andrei Stebakov 24 Nov '07

24 Nov '07

I wonder is it save to have a macro like this: (defmacro with-html (&body body) `(with-html-output-to-string (*standard-output* nil :prologue t) ,@body)) with SBCL which is multithreaded. What happens when multiple users connect to the server and the requests are served using the macro above. I mean how do multiple threads share the *standard-output* in this case? Or should I create a new stream per request? Thank you, Andrew

2 2

[hunchentoot-devel] Workaround for OpenMCL bug in ENOUGH-NAMESTRING
by Hans Hübner 15 Nov '07

15 Nov '07

Hi, OpenMCL has a bug in ENOUGH-NAMESTRING that makes Hunchentoot fail when the "/" prefix is exported from the file system using CREATE-FOLDER-DISPATCHER-AND-HANDLER. ENOUGH-NAMESTRING fails to work for URI paths having more than one component. As URI strings are not path names, I find using ENOUGH-NAMESTRING being a little fishy here anyway and I'd propose the following patch, courtesy of Kilian Sprotte: Index: misc.lisp =================================================================== --- misc.lisp (revision 2274) +++ misc.lisp (working copy) @@ -177,6 +177,11 @@ (lambda () (handle-static-file path content-type))))) +(defun enough-url (url url-prefix) + "Return the relative portion of URL relative to URL-PREFIX, similar +to what enough-pathname does for path names." + (subseq url (mismatch url url-prefix))) + (defun create-folder-dispatcher-and-handler (uri-prefix base-path &optional con tent-type) "Creates and returns a dispatch function which will dispatch to a handler function which emits the file relative to BASE-PATH that is @@ -193,8 +198,8 @@ (error "~S is supposed to denote a directory." base-path)) (flet ((handler () (let* ((script-name (url-decode (script-name))) - (script-path (enough-namestring (regex-replace-all "\\\\" scr ipt-name "/") - uri-prefix)) + (script-path (enough-url (regex-replace-all "\\\\" script-nam e "/") + uri-prefix)) (script-path-directory (pathname-directory script-path))) (unless (or (stringp script-path-directory) (null script-path-directory)

3 4