unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Leo <sdl.web@gmail.com>, emacs-devel@gnu.org
Subject: User-Agent header (was: [PATCH] New function to send a mail to the recipient at point)
Date: Mon, 25 Feb 2008 03:21:39 +0900	[thread overview]
Message-ID: <87oda6fc5o.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <v9d4qmr0tz.fsf_-_@marauder.physik.uni-ulm.de>

Reiner Steib writes:
 > On Sun, Feb 24 2008, Leo wrote:
 > 
 > > On 2008-02-24 09:05 +0000, Reiner Steib wrote:
 > >> [BTW, your User-Agent header is not confirming to RFC 2616 or the
 > >> usefor drafts.]

Of course it's conforming to RFC 2616; RFC 2616 defines HTTP headers,
not mail headers.  The drafts may define the same format (including by
reference to RFC 2616), but that's not the same as RFC 2616
conformance.

In particular, the "usefor drafts" may impose additional syntactic
restrictions or permit extensions (both unlikely) or add semantic
interpretations.  (In a trivial sense they do the latter two by
extending use of the header to mail.)

 > > How to test if it is conforming to RFC2616?

token           = 1*<any CHAR except CTLs or separators>
product         = token ["/" product-version]
product-version = token
User-Agent      = "User-Agent" ":" 1*( product | comment )

 > > ,----[ C-h v gnus-user-agent RET ]
 > > | gnus-user-agent is a variable defined in `gnus.el'.
 > > | Its value is 
 > > | "Gnus/5.130000 Emacs/23.0.60 (20080222) Fedora 8 (gnu/linux)"
 > 
 > IIRC, "Fedora 8" isn't allowed.  Probably "Fedora/8 (Fedora 8,
 > gnu/linux)" is correct.

The field value above is conformant to the RFC, although it doesn't
have the expected semantics.  It makes "Fedora" and "8" separate
products, where you would expect Fedora to be a product and 8 to be a
version.  (Consider "9" as a product token.)

I think the suggested change is simply to change the space in "Fedora
8" to a slash:

    "Gnus/5.130000 Emacs/23.0.60 (20080222) Fedora/8 (gnu/linux)"





  parent reply	other threads:[~2008-02-24 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23  0:25 [PATCH] New function to send a mail to the recipient at point Xavier Maillard
2008-02-24  9:05 ` Reiner Steib
2008-02-24  9:56   ` Leo
2008-02-24 12:33     ` User-Agent header (was: [PATCH] New function to send a mail to the recipient at point) Reiner Steib
2008-02-24 17:49       ` User-Agent header Leo
2008-02-24 18:21       ` Stephen J. Turnbull [this message]
2008-02-24 18:41         ` Bill Wohler
2008-02-24 22:44           ` Stephen J. Turnbull
2008-02-26  2:00             ` Xavier Maillard
2008-02-26  2:00   ` [PATCH] New function to send a mail to the recipient at point Xavier Maillard

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oda6fc5o.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=turnbull@sk.tsukuba.ac.jp \
    --cc=Reiner.Steib@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).