Postgres Pro
Downloads
Home   >   mailing lists

Thread: Mailing list archives redirect loop when Message-ID has slashes

Mailing list archives redirect loop when Message-ID has slashes

From
Sehrope Sarkuni
Date:
The commit notification messages from GitHub recently changed their Message-ID format to include the repository and couple other items separated by slashes. Here's an example:  pgjdbc/pgjdbc/push/refs/heads/master/7b52b0-4cd3f0@github.com

Pretty sure the messages are being archived correctly as they show up in the search list, but you can't access any of them via the mailing list web interface as all message specific URLs redirecting back to themselves:

HTTP/1.1 301 Moved Permanently
Content-Length: 0
Content-Type: text/html; charset=utf-8
Date: Mon, 18 Feb 2019 14:59:01 GMT
Server: lighttpd/1.4.45
location: /message-id/pgjdbc/pgjdbc/push/refs/heads/master/5965f3-61cc27@github.com
X-Varnish: 308386 337585
Age: 1183
Via: 1.1 varnish-v4
Strict-Transport-Security: max-age=31536000
Connection: keep-alive

Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/

Re: Mailing list archives redirect loop when Message-ID has slashes

From
Magnus Hagander
Date:


On Mon, Feb 18, 2019 at 4:38 PM Sehrope Sarkuni <sehrope@jackdb.com> wrote:
The commit notification messages from GitHub recently changed their Message-ID format to include the repository and couple other items separated by slashes. Here's an example:  pgjdbc/pgjdbc/push/refs/heads/master/7b52b0-4cd3f0@github.com

Pretty sure the messages are being archived correctly as they show up in the search list, but you can't access any of them via the mailing list web interface as all message specific URLs redirecting back to themselves:

HTTP/1.1 301 Moved Permanently
Content-Length: 0
Content-Type: text/html; charset=utf-8
Date: Mon, 18 Feb 2019 14:59:01 GMT
Server: lighttpd/1.4.45
location: /message-id/pgjdbc/pgjdbc/push/refs/heads/master/5965f3-61cc27@github.com
X-Varnish: 308386 337585
Age: 1183
Via: 1.1 varnish-v4
Strict-Transport-Security: max-age=31536000
Connection: keep-alive

Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/


Hi!

That was indeed broken. I've pushed a fix now. Some of the existing messages are still cached with the incorrect redirect, but those will automatically start working once the cache expires. Non-cached ones already work now.

Thanks for the report!

//Magnus