On Sat, 01 Dec 2001 13:20:42 -0500
Justin Sheehy <[EMAIL PROTECTED]> wrote:
> Several months ago I sent mail to mailman-users when I was trying
> to figure out how to get Mailman to run under thttpd.
Good stuff. Added to the FAQ:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01
Several months ago I sent mail to mailman-users when I was trying to
figure out how to get Mailman to run under thttpd.
I figured it out fairly quickly, but forgot to post the answer back
here. I'm doing so now, for the benefit of others who might want to
run Mailman on thttpd.
I copied the cgi
I also run a e-commerce program called Interchange (Red Hat), and it uses a CGI very
similar to Mailman (i.e., http://server.com/cgi-bin/cgifile/parameter)
So I would agree with Barry, if your other webserver program doesn't let this work, I
would tend to point the finger at the webserver, not
> "JS" == Justin Sheehy <[EMAIL PROTECTED]> writes:
JS> I'll go bother the thttpd people instead, and figure out why
JS> they don't do things that way.
Okay.
>> What does thttpd actually set SCRIPT_NAME and PATH_INFO to when
>> given a url like http://mysite.com/mailman/lis
[EMAIL PROTECTED] (Barry A. Warsaw) writes:
> Really? I think the CGI/1.1 "spec" (which really never got past draft
> status) description of SCRIPT_NAME and PATH_INFO definitely allow for
> Apache's behavior here.
You're right, it does allow it. It certainly doesn't require it, but
it doesn't
> "JS" == Justin Sheehy <[EMAIL PROTECTED]> writes:
JS> The Apache "ScriptAlias" directive and its relations, which
JS> Mailman seems to assume will be in operation, cause some other
JS> interesting behavior.
JS> If you are using Apache and follow the INSTALL, you end up
[EMAIL PROTECTED] (Barry A. Warsaw) writes:
> I've no direct experience with thttpd, but if it supports the
> "standard" CGI interface, it should be fine. If you do run into any
> gotchas (or even if it works fine), let us know and I'll add some text
> to the documentation.
So, it looks like th
[EMAIL PROTECTED] (Barry A. Warsaw) writes:
> I've no direct experience with thttpd, but if it supports the
> "standard" CGI interface, it should be fine. If you do run into any
> gotchas (or even if it works fine), let us know and I'll add some text
> to the documentation.
It supports the CGI
> "JS" == Justin Sheehy <[EMAIL PROTECTED]> writes:
JS> Is anyone known to be using Mailman with thttpd? If so, are
JS> there any known gotchas or things to look out for? I can't
JS> think of a reason why it wouldn't work, but since the Mailman
JS> docs seem to assume Apach
Hello,
A quick scan of the archives and the FAQ didn't turn anything up, so I
thought I'd ask this here.
Is anyone known to be using Mailman with thttpd? If so, are there any
known gotchas or things to look out for? I can't think of a reason
why it wouldn't work, but since the Mailman docs see
10 matches
Mail list logo
