New features for WebCompare 4.2 (fwd)

[Rob Hartill <ha...@ooo.lanl.gov>]

Fill in the blanks.
I'm not familiar enough with the 1.1 spec to know which 1.1 stuff
we support and which is experimental.

I guess this is pointless anyway since 1.1 won't be listed in this
chart until it end the beta stage.


> Message-Id: <v03006c00adb2a4639d2f@[165.227.113.247]>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Date: Sun, 5 May 1996 11:32:59 -0700
> To: (Server authors), "Paul Hoffman, Editor" <ed...@webcompare.com>
> From: "Paul Hoffman, Editor" <ed...@proper.com>
> Subject: New features for WebCompare 4.2
> Status: RO
> 
> Greetings again. Well, HTTP/1.1 is not moving as fast as we would like, but
> it is probably stable enough to start listing some of its features in
> WebCompare. I'm also adding some non-1.1 features that have been requested
> by server makers. Again, I'm always open to your suggestions for additional
> features to list in the chart.
> 
> If you missed it, the current draft, -03, is available at
> <http://www.webcompare.com/draft-ietf-http-v11-spec-03>.
> 
> The new features to be listed in WebCompare 4.2 are listed below.
> WebComapre 4.2 will be released Wednesday May 15, and you must respond by
> Monday May 13 in order to get in.
> 
> -Supports HTTP/1.1 persistent connections
> The server can keep a connection with an HTTP/1.1 client open for more than
> a single request. This is described in section 17 of draft -03 of the
> HTTP/1.1 specification.
> 
> -Understands full URIs in HTTP/1.1 requests
> HTTP/1.1 specifies that servers must be able to understand two types of
> requests: those with absolute paths (old-style locators), and those with
> full URIs. The latter is new to HTTP/1.1. This is described in section
> 9.1.2 of draft -03 of the HTTP/1.1 specification.
> 
> -Supports HTTP/1.1 PUT
> The PUT method was poorly defined in HTTP/1.0. PUT is commonly used to
> allow a remote user to add material to a Web site. In HTTP/1.1, the PUT
> method is more clearly defined in section 9.1.2 of draft -03 of the
> HTTP/1.1 specification.
> 
> -Supports HTTP/1.1 byte ranges
> HTTP/1.1 clients can request part of the content of an item using byte
> ranges, as described in section 7.14 of draft -03 of the HTTP/1.1
> specification. Byte ranges are optional for HTTP/1.1 clients and servers,
> but servers that support it will be able to restart aborted transmissions
> more easily.
> 
> -Type of server-side imagemaps
> There are two different ways to do imagemaps: the CERN way, which is used
> by servers with CERN legacies (or who prefer the CERN method) and the NCSA
> way. The difference is in the formatting of the map file.  The two types of
> map files are described at:
> CERN: http://www.w3.org/hypertext/WWW/Daemon/User/CGI/HTImageDoc.html
> NCSA: http://hoohoo.ncsa.uiuc.edu/docs/setup/admin/Imagemap.html
> Most servers support one or the other, and a few support both.
> 
> -Allows non-blocking DNS
> When a Web server accepts a new request, the operating system provides the
> server with the IP address of the client making the request. Some server
> access control policies are based on the Internet host name rather than on
> the numeric IP address, and some CGI requests require a host name. To
> reliably obtain the Internet host name takes two DNS lookups: first to
> "reverse map" the IP address to the host name, then to "forward map" the
> host name back to the IP address as a validity check. In some cases these
> lookups take several seconds even when all the computers involved are
> functioning normally. Non-blocking DNS lookup means that after accepting a
> request from a client, the server reads and parses the request in parallel
> with it looking up the DNS record (possibly using a local DNS cache). The
> server only blocks sending the response if the DNS information is required
> for security, for passing to a CGI script, for logging, and so on.
> 
> Server name:
> Version (current as of May 15):
> Supports HTTP/1.1 persistent connections:
> Understands full URIs in HTTP/1.1 requests:
> Supports HTTP/1.1 PUT:
> Supports HTTP/1.1 byte ranges:
> Type of server-side imagemaps (CERN, NCSA, Both):
> Allows non-blocking DNS:
> 
> 
> Please remember to fill out this short form for each server you have in the
> WebCompare chart. And, if you never filled out the new information for the
> 4.1 chart, please do so as soon as possible.
> 
> 
> 


--
   Windows NT  -  where programs go to die.