From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: redirect loops in archive message-id lookup |
Date: | 2017-09-15 12:48:14 |
Message-ID: | CABUevExe4h0z7wXfCyDfZxnxosOTu24RDWgNonQVgykDfzsMrw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Fri, Sep 15, 2017 at 3:25 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> I accidentally did a message-id lookup for a url of the archive. Like
> https://www.postgresql.org/message-id/http%3A/archives.
> postgresql.org/message-id/20170914065128.a5sk7z4xde5uy3ei%40alap3.
> anarazel.de/
> the result is an endless (presumably) redirect loop.
>
> Not sure if worth fixing, but thought it's worthwhile mentioning.
>
Did you get there by actually entering something in a search box somewhere,
or just by manual construction of the URL?
I think that redirect is actually generated by django before our app even
sees it. AFAICT it adds and removes the trailing slash all the time. So
it's not a trivial thing to fix...
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-09-16 18:52:34 | Small feature request for CF app |
Previous Message | Andres Freund | 2017-09-15 01:25:20 | redirect loops in archive message-id lookup |