On 1/6/22 10:35 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
It looks the right way (I have apache running in that server) to solve it. What intrigues me is the fact that I didn't change anything in the apache config or update apache itself.
That doesn't matter. With your older HyperKitty and mailman-hyperkitty the MAILMAN_ARCHIVER_KEY was sent from mailman-hyperkitty to HyperKitty as a query fragment (key=...) in the URL. The changes in HyperKitty 1.3.5 and mailman-hyperkitty 1.2.0 send it in an Authorization HTTP header instead, so before, it didn't matter if the Authorization HTTP header was dropped, now it does.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan