Skip site navigation (1) Skip section navigation (2)

Re: Message-ID should surely not be shown as a mailto: URL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Sullivan <ajs(at)commandprompt(dot)com>
Cc: pgsql-www(at)postgresql(dot)org
Subject: Re: Message-ID should surely not be shown as a mailto: URL
Date: 2008-06-09 14:38:49
Message-ID: 19073.1213022329@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-www
Andrew Sullivan <ajs(at)commandprompt(dot)com> writes:
> On Mon, Jun 09, 2008 at 02:30:55AM -0400, Tom Lane wrote:
>> I don't pretend to know what is the approved way to deal with these
>> issues, but *this* can't be best practice.

> Obviously, someone is looking for something that _looks_ like a mail
> address, attempting to munge it, and on the way through, changing it
> to a mailto: link.  I think some parsing of the RFC2821/2822 headers
> is needed first, so that one doesn't do this for things like the
> message id.   

What I'm complaining about is the logical disconnect involved in
sticking a mailto: onto an address that you have carefully made
unusable for sending mail to.  I don't have a problem with munging
all of them, just leave off the mailto decoration.

			regards, tom lane

In response to

pgsql-www by date

Next:From: Josh BerkusDate: 2008-06-09 22:39:00
Subject: Proposal: pulling newsbytes from www.pgfoundry.org
Previous:From: Alvaro HerreraDate: 2008-06-09 14:34:17
Subject: Re: Message-ID should surely not be shown as a mailto:URL

pgsql-hackers by date

Next:From: Mark Cave-AylandDate: 2008-06-09 14:44:52
Subject: Re: Strange issue with GiST index scan taking far too long
Previous:From: Simon RiggsDate: 2008-06-09 14:36:07
Subject: Re: Strange issue with GiST index scan taking far toolong

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group