Alvaro Lopez Ortega wrote:
Eric S. Johansson wrote: No, you have; the /pipermail alias needs it.
;)
hmm. I migrated something wrong (and fixed). In any case, here's an
example of what I was talking about regarding logging:
http://harvee.org/pipermail/boston-voice-users/
gave me a 404 and a log entry looks like below
192.168.0.30 - - [27/Dec/2005:20:28:53 --500] "GET
/pipermail/boston-voice-users/ HTTP/1.1" 404 0
"http://harvee.org/mailman/listinfo/boston-voice-users"; "Mozilla/5.0
(Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7"
it would be grand if there was a field for showing the filesystem path
this request would have translated to.
if the "Directory /" segment has been commented out, the mailman
CGI run. If it hasn't, then the / CGI takes priority. is it
something about script alias versus CGI handler?
Okay, the problem is that the /mailman directory handler is
inheriting the / handler properties (actually, it is a weird kind of
bug ':)
well, that's the kind of bug I am good at finding. ;-)
Anyway, I have realized of a work around; try just to define some
property inside the /mailman handler, something like this should
work, and in the meanwhile I will try to fix the issue.
that did work nicely.
No, you need just to add the default one. I mean, the one you want
to see if you access to "/mailman". I guess it is listinfo :)
a reasonable guess. :-)
Another option would be to add a Request rule to redirect the
request, something like:
I went with this redirection request and it works nicely.
well, I could always go back to hooking off of the 404 handler
which is not something I'm fond of doing.
No! no please.. I beg you! don't do that! %-)
for some reason I have an image of a dastardly villain tying a beautiful
404 handler to the rare road tracks in front of an oncoming train while
you race to save the 404 handler from certain death, dismemberment, and
heavily implied loss of virtue.
not sure if the reference is comprehensible to non-Americans especially
those not steeped in silent movies from the 1920s. See: "The perils of
Pauline".
well, I'll have you know you can save Little Miss 404 from a fate worse
than death if you allowed chaining of handlers. Each handler is allowed
to evaluate whether or not it can run and if it can, it does so and
terminates the chain. You have a precursor of this in the common
handler where you chain the file and directory handler. Generalized
chaining may or may not be desirable from your perspective but to do so
would allow you to eliminate the common handler and give me the kind of
behavior I crave (I say fiendishly twirling my mustache)
what you have today:
Directory /fiendish_villain {
DocumentRoot /var/lib/Pauline
Handler common
}
what you would have with chaining:
Directory /fiendish_villain {
DocumentRoot /var/lib/Pauline
Handler file
Handler dirlist{
show size, date
}
}
or even
Directory /fiendish_villain {
DocumentRoot /var/lib/Pauline
Handler file
Handler cgi{
scriptalias /home/esj/akasha/ak404.py
ErrorHandler on
}
}
but believe me, I do understand if that's too much like work.
--- eric (a dastardly villain)
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
