From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Subject: Re: mailto:address?subject=subject URL support
Date: 24 Oct 1996 09:49:43 +0200 [thread overview]
Message-ID: <tj7mogdco8.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Steven L Baur's message of 23 Oct 1996 11:52:00 -0700
>> "SLB" == Steven L Baur <steve@miranova.com> writes:
>> "John" == John Griffith <griffith@sfs.nphil.uni-tuebingen.de> writes:
John> I thought "X-URL" was supposed to be for *my* URL!?! Guess not.
SLB> It's an X- header. It can have whatever meaning you (or anyone else)
SLB> assigns to it.
True. RFC-822 forbids officially published field names from beginning
with "X-" which makes them safe for user-defined purposes, but still
it seems that there are some pseudo standards among "X-" fields. You
for instance, apparently use "X-Url" for your homepage. This seems to
be such a common usage that some people who use BBDB collect this
information for addresses in their database. Now to be "more"
accurate, I would have to notice whether or not the message was sent
from Netscape. Of course Netscape's use of "X-Url" would also allow
me to infer (to some degree) that someone clicked the mail button on
one of my pages and which page it was. This seems like a nice
feature. However, it would have been nice if Netscape had picked a
different field name, but I don't deny their right to use "X-Url" for
this purpose.
next prev parent reply other threads:[~1996-10-24 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-21 12:57 Per Abrahamsen
1996-10-02 14:59 ` William Perry
1996-10-21 19:23 ` Steinar Bang
1996-10-21 21:02 ` William Perry
1996-10-22 0:37 ` Lars Magne Ingebrigtsen
1996-10-22 8:40 ` Steinar Bang
1996-10-22 7:28 ` John Griffith
1996-10-22 7:44 ` Lars Balker Rasmussen
1996-10-23 18:52 ` Steven L Baur
1996-10-24 7:49 ` John Griffith [this message]
1996-10-24 15:12 ` Steven L Baur
1996-10-24 15:45 ` Per Abrahamsen
1996-10-22 13:40 William Perry
1996-10-23 8:56 ` John Griffith
1996-10-23 14:25 ` Colin Rafferty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tj7mogdco8.fsf@sfs.nphil.uni-tuebingen.de \
--to=griffith@sfs.nphil.uni-tuebingen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).