Subject: Re: mod_lisp over CGI
From: (Rob Warnock)
Date: Sat, 10 Nov 2007 05:13:48 -0600
Newsgroups: comp.lang.lisp
Message-ID: <>
Maciej Katafiasz  <> wrote:
| Rob Warnock:
| > Uh... Did you read the "Known bugs/errata/limitations:" section? Where
| > it says this?
| >   - Current "mod_lisp" protocol explicitly downcases the names of all
| >     environment variables before sending them; this program does not.
| Yes. I even wrote code to fix that. However, I think the fact that 
| mod_lisp sends, for example, a variable called "url", whereas for a CGI 
| request it's "request_uri", is even more of a problem.

De gustibus non est disputandum. I found it more of a problem that
"mod_lisp" (seemingly gratuitously) changed the names of some of
the standard CGI variables, which is why "cgi_sock.c" passes them
through unchanged. You may, of course, choose to hack up the source
of "cgi_sock.c" to make the same changes that "mod_lisp" does.

| And Hunchentoot refusing to work unfortunately confirms that.

"Use the source, Luke..."


p.s. As long as we're listing problematic(?) features of "cgi_sock.c",
note that it doesn't support "keep-alive" connections, though ISTR
that later versions of "mod_lisp" do. My app server doesn't need/want
"keep-alive", so I didn't implement it.

Rob Warnock			<>
627 26th Avenue			<URL:>
San Mateo, CA 94403		(650)572-2607