Josef Meile wrote:
If your Zope auth solution can put a header in the http response,
then you can use a custom apache logging directive to put this in your
Apache log in place of what it thinks the username is.
I put this on the log method of the medusa/http_server.py file:
If your Zope auth solution can put a header in the http response,
then you can use a custom apache logging directive to put this in your
Apache log in place of what it thinks the username is.
I put this on the log method of the medusa/http_server.py file:
Cliff Ford wrote:
This is just to report that this issue is resolved (for me). Tres
Seaver kindly provided a patch for HTTPRequest.py that makes the
environ dictionary immutable (appended below for those in a similar
position). This may have adverse consequences for applications that
rely on
On 5/18/06, Jim Washington [EMAIL PROTECTED] wrote:
Completely immutable environ is not a good choice from WSGI
point-of-view. environ can be useful for middleware information-passing.
WSGI middleware would by definition get the environ and be able to
modify it before the request gets it, so
Lennart Regebro wrote:
On 5/18/06, Jim Washington [EMAIL PROTECTED] wrote:
Completely immutable environ is not a good choice from WSGI
point-of-view. environ can be useful for middleware
information-passing.
WSGI middleware would by definition get the environ and be able to
modify it before
Hello,
Has anyone chrooted Zope/Python on OpenBSD or other and determined
what minimum devices are required for correct functionality? Willing
to share? :)
Thanks,
Michael.
___
Zope maillist - Zope@zope.org
This code on linux works without a problem
ispell = os.popen(echo + word +
| /opt/scholarpack/ancillary/ispell/bin/ispell -a)
ispell.readline
sentence = ispell.readline()
if (sentence[0] == ''):
parts = string.split(sentence, : )
gluedwords = parts[1]
words =
