From: Russ Allbery <rra@stanford.edu>
Subject: Re: Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el)
Date: Mon, 10 Feb 2003 00:41:50 -0800 [thread overview]
Message-ID: <ylk7g85xyp.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <87ptq0bkmm.fsf@unix.home> (deskpot@myrealbox.com's message of "Mon, 10 Feb 2003 11:33:21 +0300")
Vasily Korytov <deskpot@myrealbox.com> writes:
> One more related XEmacs-related patch. You may notice the difference in
> the User-Agent header of this message and the previous.
The one in this latest message is wrong, though.
User-Agent: Gnus/5.090016 (Oort Gnus v0.16) XEmacs/21.4 "Portable Code"
(linux)
"Portable Code" is not a product/version pair. Anything that isn't a
product/version pair needs to be a comment.
The User-Agent header in the mail or news context isn't really
standardized as such, but it's essentially an adoption of the User-Agent
header from HTTP. From RFC 2616:
14.43 User-Agent
The User-Agent request-header field contains information about the
user agent originating the request. This is for statistical purposes,
the tracing of protocol violations, and automated recognition of user
agents for the sake of tailoring responses to avoid particular user
agent limitations. User agents SHOULD include this field with
requests. The field can contain multiple product tokens (section 3.8)
and comments identifying the agent and any subproducts which form a
significant part of the user agent. By convention, the product tokens
are listed in order of their significance for identifying the
application.
User-Agent = "User-Agent" ":" 1*( product | comment )
Example:
User-Agent: CERN-LineMode/2.15 libwww/2.17b3
where product is:
3.8 Product Tokens
Product tokens are used to allow communicating applications to
identify themselves by software name and version. Most fields using
product tokens also allow sub-products which form a significant part
of the application to be listed, separated by white space. By
convention, the products are listed in order of their significance
for identifying the application.
product = token ["/" product-version]
product-version = token
Examples:
User-Agent: CERN-LineMode/2.15 libwww/2.17b3
Server: Apache/0.8.4
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2003-02-10 8:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18h9EM-0004hv-00@quimby.gnus.org>
2003-02-07 20:05 ` Jesper Harder
2003-02-07 20:29 ` Lars Magne Ingebrigtsen
2003-02-08 3:43 ` Vasily Korytov
2003-02-08 5:13 ` Jesper Harder
2003-02-08 20:47 ` Lars Magne Ingebrigtsen
2003-02-09 3:07 ` Vasily Korytov
2003-02-09 3:20 ` Vasily Korytov
2003-02-10 8:33 ` Vasily Korytov
2003-02-10 8:41 ` Russ Allbery [this message]
2003-02-10 9:10 ` Vasily Korytov
2003-02-11 1:32 ` Lars Magne Ingebrigtsen
2003-02-11 5:10 ` Jesper Harder
2003-02-11 13:23 ` User-Agent string (was: Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el)) Reiner Steib
2003-02-12 10:19 ` User-Agent string Vasily Korytov
2003-02-22 20:27 ` Lars Magne Ingebrigtsen
2003-02-24 21:12 ` Reiner Steib
2003-02-24 22:18 ` Vasily Korytov
2003-02-27 14:50 ` Reiner Steib
2003-02-27 19:33 ` Vasily Korytov
2003-02-28 19:26 ` Reiner Steib
2003-03-01 23:06 ` Frank Haun
2003-03-03 16:18 ` Reiner Steib
2003-02-25 10:26 ` Kai Großjohann
2003-02-11 7:23 ` Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el) Vasily Korytov
2003-02-22 20:28 ` Lars Magne Ingebrigtsen
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=ylk7g85xyp.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).