On 03/22/2016 06:07 PM, Mark Sapiro wrote:
Trying again. The last one actually succeeded in getting an archive url but got a 301 and then a 400 on the actual archiving.
On 03/22/2016 06:20 PM, Mark Sapiro wrote:
On 03/22/2016 06:07 PM, Mark Sapiro wrote:
Trying again. The last one actually succeeded in getting an archive url but got a 301 and then a 400 on the actual archiving.
Trying yet again w/ USE_SSL = False as before but still
base_url: https://lists.mailman3.org/archives
On 03/22/2016 06:20 PM, Mark Sapiro wrote:
On 03/22/2016 06:07 PM, Mark Sapiro wrote:
Trying again. The last one actually succeeded in getting an archive url but got a 301 and then a 400 on the actual archiving.
Ooops. I must have forgotten to refresh a page this one (to which I'm replying) did get archived.
On 03/22/2016 06:33 PM, Mark Sapiro wrote:
On 03/22/2016 06:20 PM, Mark Sapiro wrote:
On 03/22/2016 06:07 PM, Mark Sapiro wrote:
Trying again. The last one actually succeeded in getting an archive url but got a 301 and then a 400 on the actual archiving.
Ooops. I must have forgotten to refresh a page this one (to which I'm replying) did get archived.
OK. I think all is working as it should now with USE_SSL = True
The missing piece was in mailman-hyperkitty.cfg. I originally had
base_url: http://127.0.0.1/archives
Changing that to
base_url: https://lists.mailman3.org/archives
allowed the plugin to communicate with HyperKitty via https without certificate errors or losing POST data to redirects.
participants (1)
-
Mark Sapiro