Mailman "webcreate" page and proxy-ing problems
I've been running Mailman 2.0.x through a proxy to the /localhost/ so as to only need one single install of Mailman across a number of virtual domains for sometime now. it's worked well under 2.0.x... one install - many domains.
I've recently upgraded to Python 2.3 and the Mailman 2.1.5 release....all the old /admin/ /listinfo/ etc.. pages continue to work with this scheme... However, the list creation page that was introduced with the 2.1 code base is lifting it's page host-name references out of the proxy, rather than the calling page. Submitting the form, or clicking the links on the bottom of the page all try to direct the browser to /localhost/. I dont see this behaviour on the other pages.
Is there some mm_cfg.py setting that I've forgotten to override?... or a template I can force?
I do have a
add_virtualhost('apollo.host-ops.com', 'apollo.host-ops.com')in the bottom of the mm_cfg.py, and
DEFAULT_EMAIL_HOST
DEFAULT_URL_HOSTare both set to the above inside Defaults.py, so I have no need to override them....
Any help would be appreciated.
At 1:13 AM -0400 2004-09-30, scott@nexus-iservices.com wrote:
I've been running Mailman 2.0.x through a proxy to the /localhost/ so as to only need one single install of Mailman across a number of virtual domains for sometime now. it's worked well under 2.0.x... one install - many domains.
I think you may find FAQ 4.47 in the Mailman FAQ Wizard at http://www.python.org/cgi-bin/faqw-mm.py to be of interest. So far as I know, these are the only virtual domain hosting solutions possible with Mailman.
-- Brad Knowles, brad@stop.mail-abuse.org
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755SAGE member since 1995. See http://www.sage.org/ for more info.
Thanks Brad -- I found a one line solution that solves my problem
a minor change to Utils.py:
^L def get_domain(): host = os.environ.get('HTTP_X_FORWARDED_HOST', os.environ.get('SERVER_NAME')) # host = os.environ.get('HTTP_HOST', os.environ.get('SERVER_NAME')) port = os.environ.get('SERVER_PORT') # Strip off the port if there is one
And now all the links are fine.
I know its not the "BEST" solution... and I'm sure Barry and the rest of the development team can make it work better under all circumstances (ie, when the host is not proxy'd) -- but this seems to solve my problems nicely now.
-- note -- this does not solve the total virtualization problem... lists are still unique to the server they reside on, but it does solve the need to install mailman against every domain...
-----Original Message----- From: Brad Knowles [mailto:brad@stop.mail-abuse.org] Sent: September 30, 2004 9:26 AM To: scott-brown@rogers.com Cc: Mailman-Users@python.org; scott@nexus-iservices.com Subject: Re: [Mailman-Users] Mailman "webcreate" page and proxy-ing problems
At 1:13 AM -0400 2004-09-30, scott@nexus-iservices.com wrote:
I've been running Mailman 2.0.x through a proxy to the /localhost/ so as to only need one single install of Mailman across a number of virtual domains for sometime now. it's worked well under 2.0.x... one install - many domains.
I think you may find FAQ 4.47 in the Mailman FAQ Wizard at http://www.python.org/cgi-bin/faqw-mm.py to be of interest. So far as I know, these are the only virtual domain hosting solutions possible with Mailman.
-- Brad Knowles, brad@stop.mail-abuse.org
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755SAGE member since 1995. See http://www.sage.org/ for more info.
participants (2)
-
Brad Knowles -
scott＠nexus-iservices.com