unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Do you understand this?
Date: Mon, 7 Mar 2005 10:37:44 -0500 (EST)	[thread overview]
Message-ID: <m1D8KIi-0004RGC@rattlesnake.com> (raw)
In-Reply-To: <u8y504bpi.fsf@jasonrumney.net> (message from Jason Rumney on Sun, 06 Mar 2005 23:05:29 +0000)

Thanks to Andreas, Jason, and Nic I think I now understand the rfc2616
HTTP specification a great deal better than before.

Perhaps we should add the following to

    emacs/man/url.texi

after the text saying:

    @node HTTP language/coding
    @subsection Language and Encoding Preferences

    HTTP allows clients to express preferences for the language and
    encoding of documents which servers may honour.

Is this now an accurate description?


An @samp{Accept:} or @samp{Accept-Charset} statement or @samp{headers}
allows you to specify the priority or weighing of the type of
statement you would like to accept.

In contrast to their precedence in English text, commas separate
@emph{bigger} groupings than semi-colons, which are used to prefix
weightings or priority values.  Priority values go from 0.0 to 1.0,
with 1.0 being highest.  When a priority or weighting value is not
listed the value is presumed to be 1.0.  Moreover, an @samp{Accept:}
or @samp{Accept-Charset} list need not be in priority or precedence
order.

@need 800
@noindent
Thus, an accept statement such as

@smallexample
Accept: text/plain;
        q=0.5, text/html, text/x-dvi;
        q=0.8, text/x-c
@end smallexample

@need 1000
@noindent
could be reformatted as

@smallexample
Accept: text/plain; q=0.5,
        text/x-dvi; q=0.8,
        text/html ; q=1.0,
        text/x-c  ; q=1.0
@end smallexample

@noindent 
This latter expression shows the list in order from lower to higher
priority.  Both @samp{text/html} and @samp{text/x-c} are of equal
(and highest) priority.

When sent in an HTTP request for a resource, the above @samp{Accept:}
statement tells the server that the user prefers to either an HTML or
text/x-c document.  If neither of those reprsentations is available,
then DVI is next preference.  If none of those three are available,
then plain text should be sent.  If neither plain text, DVI, HTML nor
x-c are available, then the server's response should indicate that it
is failing to find a representation that satisfies the request.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  reply	other threads:[~2005-03-07 15:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 19:11 Do you understand this? Richard Stallman
2005-03-06 20:44 ` Nic Ferrier
2005-03-06 22:32   ` Robert J. Chassell
2005-03-06 22:58     ` Andreas Schwab
2005-03-06 23:05     ` Jason Rumney
2005-03-07 15:37       ` Robert J. Chassell [this message]
2005-03-07 17:10         ` Jason Rumney
2005-03-07 23:46           ` Robert J. Chassell
2005-03-08  0:34             ` Nic Ferrier
2005-03-08 18:41               ` Robert J. Chassell
2005-03-09 16:58                 ` Richard Stallman
2005-03-06 23:12     ` Nic Ferrier

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=m1D8KIi-0004RGC@rattlesnake.com \
    --to=bob@rattlesnake.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).