On 6/24/16 8:18 AM, John Griessen wrote:
On 06/18/2016 02:10 PM, Mark Sapiro wrote:
I think in the long run, you'd be better off with Mailman 3.
Is it time to install version 3?
Is that going to work with different rewrite rules behind nginx?
Will it cure my problem with moderation and nginx and https?
If you are going to post to mailman-users@mailman3.org, please join the list. That way you will see replies to your posts such as the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/GRCBWKJPVEFEIP6RT7OB3OKQOD54OX2X/>. You can join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>.
The reply addresses your first question.
With respect to your other questions, I think you have resolved your http/https issues in MM 2.1. MM 3 works similarly, but perhaps more obviously. When you create a domain in MM3 you specify a web URL for the domain's web UI. If this is an https URL, you won't have the issues you saw.
There is another way to address this, and that's in the web server (nginx in your case) when you configure the web server to redirect http to https with a 301 Moved Permanently status (or maybe a 302), this tells the browser to issue a GET for the new URI, even if the original request was a POST. Thus the POST data is lost. That is the underlying issue. If instead, you configure the web server to issue a 308 Permanent Redirect instead, this tells the browser to issue a request for the new URI using the original GET/POST/whatever method, so the browser SHOULD reissue the original POST to the new URI. This will work provided the browser recognizes 308 and acts appropriately.
Thus, fixing the scheme in Mailman is the more reliable solution as it doesn't depend on the browser knowing what to do.
See, e.g., <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan