i found this situation:
whoami, pwd: http, /usr/local/moin/share/moin/cgi-bin
REMOTE_HOST=localhost
REMOTE_ADDR=127.0.0.1
REMOTE_PORT=25178
HTTP_USER_AGENT=Lynx/2.8.5dev.7 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.6c
HTTP_HOST=spotteswoode.dnsalias.org
REQUEST_URI=/moin/cgi-bin/printenv
SERVER_SOFTWARE=Mathopd/1.4b20
SERVER_PROTOCOL=HTTP/1.0
EXTERN_EXECUTABLE=/usr/local/moin/share/moin/cgi-bin/moin.cgi
REQUEST_METHOD=GET
SERVER_ADDR=127.0.0.1
PYTHONPATH=/usr/local/moin/lib/python2.0/site-packages
SERVER_PORT=8887
SCRIPT_NAME=/moin/cgi-bin/printenv
SERVER_NAME=spotteswoode.dnsalias.org
in cgimain.py for example, i find this hardcoded:
query = ...unquoteWikiname(os.environ.get('QUERY_STRING', '')) \
or config.page_front_page
word_re_str = r"([%s][%s]+){2,}" % (config.upperletters, config.lowerletters)
this is partially responsible for the fact that i constantly get only one
page delivered in an editable, usable fashion: the frontpage.
does apache define the way the CGI implementation has to be used? mathopd,
boa, thttpd all claim CGI1.1 conformity, but moin seems to run
out-of-the-box only on apache. i think at least the definition of what
constitutes a WikiWord should be configurable, and also where the path-part
of the query-string can be found. this is python-world, remember?
SCRIPT_NAME=/moin/cgi-bin/printenv (eg; is what mathopd lets a cgi see)
REQUEST_URI=/moin/cgi-bin/printenv
if all this sounds angry to you, it is not really because of moin, but
rather leftovers of twiki, where i know this game from. but perl is next
to unmanagable compared to python, which is why my hopes with moin are much
higher. also, busily updating something - twiki announced betas weekly at
times! - may look like a project beeing "actively developed", but with
twiki it was hopping featurism. not with moin, this is comparibly solid.
'nuf said :)
--
clemens fischer
evil is even, truth is an odd number and death is a full stop.
<- miles 'na gopaleen
