tbnl-devel July 2009

tbnl-devel@common-lisp.net

8 participants
8 discussions

[hunchentoot-devel] Hunchentoot on PORT 80
by Phil Marneweck 18 Sep '09

18 Sep '09

Hi Yesterday I tried to run hunchentoot on port 80 for the first time, but a get a "Permission Denied" error when hunchentoot tries to bind to port 80. Between the #ubuntu and #lisp guys we established that nothing else was running on port 80 and that I was indeed running as root. Everybody agreed that it must be that permissions gets dropped some where along the line. Searching the web regarding dropped permissions got me no where. So I was wondering if anybody else got this configuration to work on port 80 and could share their experience with me please. I have a clean ubuntu server, no apache or anything installed. I have an in init.d script that starts up a screen session which runs swank and start up stuff to load hunchentoot etc ie swank-daemon from clwiki. Regards Phil

6 7

[hunchentoot-devel] Problem with late calls to POST-PARAMETERS
by Peter Seibel 21 Aug '09

21 Aug '09

I ran into a problem converting some of my code to run with Hunchentoot 1.0. This patch fixes it and -- as far as I can tell after a bit of poking around -- is possibly righteous. What do you think? The basic problem that I ran into is explained in the comment in the patch. -Peter diff -r 635083ac9419 hunchentoot/request.lisp --- a/hunchentoot/request.lisp Sun May 31 11:31:25 2009 -0700 +++ b/hunchentoot/request.lisp Mon Jun 01 14:19:19 2009 -0700 @@ -346,7 +346,12 @@ (get-parameters request)) (defmethod post-parameters :before ((request request)) - (maybe-read-post-parameters :request request)) + ;; Force here because if someone calls POST-PARAMETERS they actually + ;; want them, regardless of why the RAW-POST-DATA has been filled + ;; in. (For instance, if SEND-HEADERS has been called, filling in + ;; RAW-POST-DATA, and then subsequent code calls POST-PARAMETERS, + ;; without the :FORCE flag POST-PARAMETERS would return NIL.) + (maybe-read-post-parameters :request request :force t)) (defun post-parameters* (&optional (request *request*)) "Returns an alist of the POST parameters associated with the REQUEST -- Peter Seibel http://www.codersatwork.com/ http://www.gigamonkeys.com/blog/

6 15

[hunchentoot-devel] Exporting HANDLER-DONE
by Leslie P. Polzer 29 Jul '09

29 Jul '09

This is a useful throw tag that should be part of the public API. Would anyone object against exporting this in the next version? Leslie -- http://www.linkedin.com/in/polzer

3 3

[hunchentoot-devel] REF: Re: Hunchentoot 1.0.0 on Lispworks Profes sional for windows
by Alexandre Paes 10 Jul '09

10 Jul '09

Hi only after replying did i see eli suggestion but although i was usind chunga 0.4.3 after upgrading the error is the same. I noticed however that if i run the testing code from lw ide instead of console + emacs i end um in the debugger with the error: ; Request home page Error: no status line - probably network error i'm using drakma 1.0.0, chunga 1.0.0 and flexi-streams 1.0.7. i am getting frustrated. One whole day trying to get some html served. thanks, Alexandre Paes -- msg. original -- Assunto: Re: [hunchentoot-devel] Hunchentoot 1.0.0 on Lispworks Professional for windows De: Hans Hübner <hans.huebner(a)gmail.com> Data: 03.07.2009 21:08 Alexandre, did you verify that you have the right versions of the dependencies, as Eli rightfully suggested? -Hans On Fri, Jul 3, 2009 at 21:57, Alexandre Paes<alex.paes(a)streetdogstudio.com> wrote: > Quoting Hans Hübner <hans.huebner(a)gmail.com>: > >> Not that the blank page is cool or anything, but did you actually >> install any handlers? You might try loading the :hunchentoot-test >> package and then open http://localhost:9000/hunchentoot/test >> >> Let us know if the problem persists. >> >> -Hans > > Hi Hans, after trying out loading the :hunchentoot-test like you > suggested, the result is that the test suite hangs after printing "; > Request home page", i guess this means there should be some problem > with the connection to localhost? i also tried using 127.0.0.1 > directly but got the exact same result. any more ideas of how i can > debug the problem? > > Thanks, > > Alexandre Paes > > > > > _______________________________________________ > tbnl-devel site list > tbnl-devel(a)common-lisp.net > http://common-lisp.net/mailman/listinfo/tbnl-devel > _______________________________________________ tbnl-devel site list tbnl-devel(a)common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel

2 2

[hunchentoot-devel] ETag, Cache-Control, and/or Expires headers
by Patrick May 07 Jul '09

07 Jul '09

I need to prevent an intermediate cache from caching a static audio file I'm providing via register-static-file. What's the easiest way to set these for every reply (changing it dynamically, in the case of ETag)? Thanks, Patrick

2 4

[hunchentoot-devel] Hunchentoot effective DOS-attack
by Peter Stiernström 06 Jul '09

06 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I don't know if this have come up earlier or if it is a known problem. If so I am sorry for bringing it up again. A quick look through the archives turned up a non-caught sbcl socket timeout error with the obvious fix of adding an error translation to the usocket sbcl backend error map. I expect this to be somewhat similar. When stressing hunchentoot with a number of connection like so: for i in $(seq 1 20); do nmap -sT -p 80 <hostname> ;done Hunchentoot (last 1.0 release) stops responding after not having caught a SB-BSD-SOCKETS:NOT-CONNECTED-ERROR thus being easily DOSed. I was hoping that there would be an obvious similar mapping missing but I don't know my way around hunchentoot to figure out what to map SB-BSD-SOCKETS:NOT-CONNECTED-ERROR to. I am seeing this problem on a regular basis and for now it always prompts a full restart. I am using usocket 0.4.1 with hunchentoot 1.0.0. /Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpN54YACgkQ0brSZD05ZzARvACfe7SP+QJeHyyQg2zVMKaDL7PI Z8sAn26so+rYt9eviL/x+E0a6XYORbig =4rny -----END PGP SIGNATURE-----

2 13

[hunchentoot-devel] REF: Re: REF: Re: Hunchentoot 1.0.0 on Lispwor ks Profes sional for windows
by Alexandre Paes 03 Jul '09

03 Jul '09

Thanks again Hans, i will try to follow the steps you describe and see where that leads. By the way, lisp is a real passion for me so rest assured i'm not quitting. thanks, Alexandre Paes -- msg. original -- Assunto: Re: [hunchentoot-devel] REF: Re: Hunchentoot 1.0.0 on Lispworks Profes sional for windows De: Hans Hübner <hans.huebner(a)gmail.com> Data: 03.07.2009 23:10 Alexandre, let's see, here is what I did: - Get Lispworks 5.1 for Windows from lispworks.com, install on my Vista laptop - svn co http://bknr.net/svn/ediware - set up asdf:*central-registry* - (asdf:oos 'asdf:load-op :hunchentoot-test) - load http://localhost:9000/hunchentoot/test in browser Everything worked as expected. The svn version of Hunchentoot and its dependencies are sufficiently close to the released versions to make me believe that you're still using an old version of one of the dependencies. I'm sorry to hear that you're having a hard time getting Hunchentoot to run, but I think you can rest assured that this is not because it does not work. It is more likely that you need to acquire some more experience with your Lisp environment. Please don't give up! -Hans

1 0

[hunchentoot-devel] Hunchentoot 1.0.0 on Lispworks Professional for windows
by Alexandre Paes 03 Jul '09

03 Jul '09

Hi everyone, I've tried searching the list archives but found no solution or even indication of what my problem is. I'm trying to run a small web app locally from Hunchentoot 1.0.0 on Lispworks 5.1.2 on Windows XP, i set asdf and installed hunchentoot and it loads perfectly but the thing is that once i run test code shown in Hunchentoot homepage: (hunchentoot:start (make-instance 'hunchentoot:acceptor :port 9000)) It simply returns to the repl and when looking at the process browser i can see the Hunchentoot process standing there with "Waiting for connection" status. But when i then go to http://localhost:9000 in firefox i simply get a blank page. Does anyone have any idea what might be causing this? I the windows firewall disabled and added exceptions to the mcaffee firewall, and have even disabled mcaffee firewall but the result is always the same. Thanks in advance, Alexandre Paes

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

tbnl-devel July 2009