W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1996

Re: 5.1.2 Request-URI

From: Dave Kristol <dmk@allegra.att.com>
Date: Thu, 25 Apr 96 16:14:24 EDT
Message-Id: <9604252014.AA05199@zp.tempo.att.com.tempo.att.com>
To: fielding@avron.ICS.UCI.EDU
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/340
  > > [DMK]
  > > I would think that for the *http* specification, particularly for an
  > > origin server, there are the following additional requirements that
  > > are currently unstated:
  > > 
  > > - absoluteURI must be an http_URL (3.2.2)
  > > - (should https_URL and shttp_URL also be mentioned?)
  > > - host must be the FQDN of the host to which the request is sent

"Roy T. Fielding" <fielding@avron.ICS.UCI.EDU> wrote:
  > Absolutely NOT on all three items.  HTTP is used as a generic
  > interface protocol for resolving any URI, including URNs
  > (which do not have a hostname) and any number of other
  > identifiers which follow the URI syntax.  That syntax is correctly
  > described in the spec.
I said "particularly for an origin server".  I believe an *origin
server* sees either a relativeURI or an absoluteURI in the form of an
http_URL on the request line.  I'm trying to nail down what an origin
server should expect to see.  It should be specified somewhere.

Dave Kristol
Received on Thursday, 25 April 1996 13:29:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:16 UTC