On Sat, Mar 2, 2013 at 3:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Sat, Mar 2, 2013 at 3:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> While we're griping about that sort of thing ... URLs like this used to
>>> work to fetch a message by message-id:
>>>
http://www.postgresql.org/list/message-by-id.php?q=CAK3UJRGZfoRJsVBuhwQMAQbk1MPXx5TdOq24NxqCCGB4zQ3Ezg%40mail.gmail.com/
>
>> Exactly what was the original URLs you guys tried? Becuase both those
>> look like the result of having been rewritten/redirected... (Possibly
>> incorrectly so..)
>
> In my case that was the original URL. I have a link on my home page for
> going straight to a copied-and-pasted message ID, which works like this:
>
> <form action="http://archives.postgresql.org/message-by-id.php"
> method="get" id="goto-message-id">
> Archived message ID <input type="text" name="q" size="60" />
> </form>
Not quite. That form generates an url to archives.postgresql.org - so
what you pasted above clearly is the redirected version.
I noticed that this one is different from the one Josh Kupershmidt
reported (that one was for msgtxt.php), so if your custom for was the
only case where this one was actually hit, I'm not sure it's worth
fixing, since you can easily fix it per below.
Have you or anybody else seen this URL pattern in links that are
actually stored anywhere?
> It's no trouble to change the form parameters, but this method requires
> URLs that look like "...?something=messageid". I don't know if the new
> site layout accepts anything like that.
If you input any messageid in the general search box, it will do the
right thing transparently now. So you can just put
http://www.postgresql.org/search/ as your target for the search.
--Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
