From: Steve Youngs <steve@youngs.au.com>
Subject: Re: Using versions instead of XEmacs codenames in User-Agent
Date: Mon, 10 Jan 2005 19:20:23 +1000 [thread overview]
Message-ID: <microsoft-free.874qhptzc8.fsf@youngs.au.com> (raw)
In-Reply-To: <87wtulzndx.fsf@obelix.mork.no> (=?iso-8859-1?Q?Bj=F8rn?= Mork's message of "Mon, 10 Jan 2005 09:42:02 +0100")
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
* Bjørn Mork <bmork@dod.no> writes:
> Steve Youngs <steve@youngs.au.com> writes:
>> * Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>
>> > On Sun, Jan 09 2005, Steve Youngs wrote:
>> >> The default settings should give a User-Agent header similar to the
>> >> one in this message's headers.
>>
>> > | User-Agent: Gnus/5.110003 (No Gnus v0.3) SXEmacs/22.1.1 "Aston Martin" (linux)
>>
>> > Is a quoted string like "Aston Martin" allowed in RFC 2616?
>>
>> ,----[ from RFC 2616 ]
[...]
>> Going by that, using quoted text "like this" should be fine.
> No, it isn't. quoting more from RFC 2616:
> token = 1*<any CHAR except CTLs or separators>
> separators = "(" | ")" | "<" | ">" | "@"
> | "," | ";" | ":" | "\" | <">
> | "/" | "[" | "]" | "?" | "="
> | "{" | "}" | SP | HT
>> > Upto now, we had it inside the bracket:
>> > | [...] XEmacs/21.4 (Security Through Obscurity, berkeley-unix)
>>
>> Yep, however, IMHO, this...
>>
>> SXEmacs/22.1.1 (Aston Martin, berkeley-unix)
>>
>> doesn't look anywhere near as nice as...
>>
>> SXEmacs/22.1.1 "Aston Martin" (berkeley-unix)
> Maybe. But it doesn't really matter since the first version uses a
> perfectly legal comment while the second is an invalid User-Agent
> field.
OK, now I'm really confused. Because going by what you quoted about
tokens and separators, aren't both of them invalid? And if not, why
not?
Also, what the hell does RFC 2616 - "Hypertext Transfer Protocol --
HTTP/1.1" have to do with email headers? I honestly don't understand
that at all?
BTW, I really don't mind whether we use `"codename" (platform)'
or `(codename, platform)'.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Te audire no possum. |
| Musa sapientum fixa est in aure. |
|----------------------------------<steve@youngs.au.com>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-01-10 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 1:49 [PATCH] SXEmacs User-Agent string Steve Youngs
2005-01-06 13:41 ` Using versions instead of XEmacs codenames in User-Agent (was: [PATCH] SXEmacs User-Agent string) Reiner Steib
2005-01-06 23:00 ` Using versions instead of XEmacs codenames in User-Agent Katsumi Yamaoka
2005-01-06 23:29 ` Steve Youngs
2005-01-08 18:09 ` Reiner Steib
2005-01-09 1:28 ` Steve Youngs
2005-01-09 20:55 ` Reiner Steib
2005-01-09 23:09 ` Steve Youngs
2005-01-10 8:42 ` Bjørn Mork
2005-01-10 9:20 ` Steve Youngs [this message]
2005-01-10 10:39 ` Bjørn Mork
2005-01-10 15:07 ` Reiner Steib
2005-01-10 23:29 ` Steve Youngs
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=microsoft-free.874qhptzc8.fsf@youngs.au.com \
--to=steve@youngs.au.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.
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).