Hi Tokio,
I'm not so sure about this change. It breaks the ability to access
the web page urls by both the wsgi path and the apache ScriptAlias
path at the same time. I've tried to make sure that worked because
it's pretty useful for debugging.
Well, I was inclined to abolish ScriptAlias (CGI) method because of SGUI complexities. ;-)
I'm trying to keep the principle that all internal web page urls are
relative, which is why we currently try to figure out the prefix to
the script and then reproduce that in the cookie path (see
SecurityManager.py). I've also been thinking about trying to get rid
of mlist.web_page_url (I don't much like hard coding that in the
list's data).I understand that we'll need absolute paths in the email
notifications, and I've read the note about not exposing wsgi_app
interface to the internet. I'm not sure I agree with the latter
though, and besides, I'd like us to be as flexible as possible for
wsgi integration. I think we should try to find some other way to do
the email notification urls and keep GetScriptURL() returning
relative paths.
Like VirtualHostMonster in Zope?
E.g. when I try to use r8090 via the Apache ScriptAlias path, I end
up getting three slashes between the host and the 'mailman' prefix.
Oops, I'll try restore ScriptAlias.
- -Barry
-- Tokio Kikuchi, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/