Alternate URL hostname in web UI
Hello, I'm trying to set up the mailman (2.1.9) web UI behind a load balancer in order to offload the TLS to it (because this is an ancient machine which doesn't support modern TLS versions, and newer browsers are complaining about it). I need all the links in the web UI to use the new hostname that's in front of the loadbalancer, instead of the actual hostname behind the loadbalancer. Am I understanding correctly that DEFAULT_URL_HOST in mm_cfg.py would be the way to accomplish that? And would that affect only the URLs used in the web UI, it wouldn't change anything about the actual mail handling under the hood?
Kevin Bowen kevin.t.bowen@gmail.com kevin@ucsd.edu
On 7/27/20 12:22 PM, Kevin Bowen wrote:
Hello,
Hi,
I'm trying to set up the mailman (2.1.9) web UI behind a load balancer in order to offload the TLS to it (because this is an ancient machine which doesn't support modern TLS versions, and newer browsers are complaining about it). I need all the links in the web UI to use the new hostname that's in front of the loadbalancer, instead of the actual hostname behind the loadbalancer. Am I understanding correctly that DEFAULT_URL_HOST in mm_cfg.py would be the way to accomplish that? And would that affect only the URLs used in the web UI, it wouldn't change anything about the actual mail handling under the hood?
I can't speak directly to the DEFAULT_URL_HOST.
Does the load balancer support rewriting things as traffic passes through it? I know it's possible to get Apache to do this.
-- Grant. . . . unix || die
I'm not sure. I suspect it might be possible, but I'm not sure how, so if I could just have mailman itself present the alternate URL, that would be simpler.
Kevin Bowen kevin.t.bowen@gmail.com kevin@ucsd.edu
On Mon, Jul 27, 2020 at 1:46 PM Grant Taylor via Mailman-Users < mailman-users@python.org> wrote:
On 7/27/20 12:22 PM, Kevin Bowen wrote:
Hello,
Hi,
I'm trying to set up the mailman (2.1.9) web UI behind a load balancer in order to offload the TLS to it (because this is an ancient machine which doesn't support modern TLS versions, and newer browsers are complaining about it). I need all the links in the web UI to use the new hostname that's in front of the loadbalancer, instead of the actual hostname behind the loadbalancer. Am I understanding correctly that DEFAULT_URL_HOST in mm_cfg.py would be the way to accomplish that? And would that affect only the URLs used in the web UI, it wouldn't change anything about the actual mail handling under the hood?
I can't speak directly to the DEFAULT_URL_HOST.
Does the load balancer support rewriting things as traffic passes through it? I know it's possible to get Apache to do this.
-- Grant. . . . unix || die
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
On 7/27/20 11:22 AM, Kevin Bowen wrote:
Am I understanding correctly that DEFAULT_URL_HOST in mm_cfg.py would be the way to accomplish that? And would that affect only the URLs used in the web UI, it wouldn't change anything about the actual mail handling under the hood?
That is correct, but you also need to run fix_url after changing DEFAULT_URL_HOST. See https://wiki.list.org/x/4030616.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks. One other question: in my existing mm_cfg.py I have all three of the following: DEFAULT_HOST_NAME = 'mailman.domain.com' DEFAULT_URL_HOST = 'mailman.domain.com' DEFAULT_EMAIL_HOST = 'mailman.domain.com'
In Defaults.py, it explains that DEFAULT_HOST_NAME is deprecated, but the language is unclear as to what overrides what. In this use case, do I need to change DEFAULT_HOST_NAME as well, or only DEFAULT_URL_HOST?
Kevin Bowen kevin.t.bowen@gmail.com kevin@ucsd.edu
On Mon, Jul 27, 2020 at 9:19 PM Mark Sapiro mark@msapiro.net wrote:
On 7/27/20 11:22 AM, Kevin Bowen wrote:
Am I understanding correctly that DEFAULT_URL_HOST in mm_cfg.py would be the way to accomplish that? And would that affect only the URLs used in the web UI, it wouldn't change anything about the actual mail handling under the hood?
That is correct, but you also need to run fix_url after changing DEFAULT_URL_HOST. See https://wiki.list.org/x/4030616.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
On 7/28/20 8:02 AM, Kevin Bowen wrote:
Thanks. One other question: in my existing mm_cfg.py I have all three of the following: DEFAULT_HOST_NAME = 'mailman.domain.com' DEFAULT_URL_HOST = 'mailman.domain.com' DEFAULT_EMAIL_HOST = 'mailman.domain.com'
In Defaults.py, it explains that DEFAULT_HOST_NAME is deprecated, but the language is unclear as to what overrides what. In this use case, do I need to change DEFAULT_HOST_NAME as well, or only DEFAULT_URL_HOST?
Just remove DEFAULT_HOST_NAME from mm_cfg.py entirely. It has nothing to do with the web host. It is the former name for what is now called DEFAULT_EMAIL_HOST. If you leave it, it will override anything you set for DEFAULT_EMAIL_HOST for new list creation.
The situation with DEFAULT_URL_HOST is more complicated. There was a former DEFAULT_URL setting which was used to set the list's web_page_url at list creation time. It was the full URL. The current setting is DEFAULT_URL_HOST which is interpolated into DEFAULT_URL_PATTERN to make the setting for the list's web_page_url at list creation time.
fix_url which you need to run after changing these things does not consider DEFAULT_HOST_NAME or DEFAULT_URL at all and these should not be set in mm_cfg.py in any case.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Grant Taylor -
Kevin Bowen -
Mark Sapiro