public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dave Page <[email protected]>
To: PostgreSQL WWW <[email protected]>
Subject: Fwd: [webmaster] Extra slash in links on archives.postgresql.org
Date: Sun, 10 May 2009 11:40:31 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Can someone look at this please?
---------- Forwarded message ----------
From: Noah Misch
Date: Sat, May 9, 2009 at 7:43 PM
Subject: [webmaster] Extra slash in links on archives.postgresql.org
To: [email protected]
The links on the per-message pages at archives.postgresql.org have an extra
slash. Consider `/pgsql-hackers/2009-05/msg00425.php'. The link to this page
from `/pgsql-hackers/2009-05/threads.php' is:
http://archives.postgresql.org/pgsql-hackers/2009-05/msg00425.php
But the link from `/pgsql-hackers/2009-05/msg00422.php' (previous message in the
thread) is:
http://archives.postgresql.org//pgsql-hackers/2009-05/msg00425.php
----------------------------->_<-- extra slash
This interferes with Firefox showing links as visited; it treats these as
distinct locations. I tend to grab the head of a thread from the threads index,
then walk down the thread by "Next by thread" links. I used to use link
coloring to identify messages added to a thread since I last read it. When this
extra slash appeared (in the last 1-3 months), this strategy no longer worked:
Firefox regarded links in the thread index as unrelated to the links in the
individual message pages.
Please consider changing the tool that generates these pages to render the links
consistently across the index and message pages.
Thanks,
nm
(I should probably use the news server instead.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFKBc7eVphiekB/u2YRAoLMAJ9yFvr/qA6AQC02Y8VpBrrU9E2rOQCdH4+u
hzYt1XrtQIjcrOBWNRt4DTM=
=JTY6
-----END PGP SIGNATURE-----
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Fwd: [webmaster] Extra slash in links on archives.postgresql.org
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox