HTTP/1.1 Conformance Problems

While testing the libwww and Jigsaw HTTP/1.1 compliant reference implementations, we have run into some conformance problems with HTTP/1.0 applications.

NCSA Server 1.5.x

The NCSA server does not send back a version number when responding to a HTTP/1.1 request. This means that the Response Line lacks a token. An example of a reply looks like this. The NCSA server team have been notified about the problem.

	HEAD / HTTP/1.1
 	Host: www.ncsa.uiuc.edu
 	HTTP 200 Document follows
 	Date: Tue, 24 Sep 1996 12:56:40 GMT
 	Server: NCSA/1.5.1
 	Last-modified: Wed, 18 Sep 1996 16:44:29 GMT
 	Content-type: text/html
 	Content-length: 8641

Hyper-G W3 Gateway V 2.51

This is the response we get from a Hyper-G gateway

	GET /home;sk=17062E7B HTTP/1.1
 	Host: hyperg.obg.ed.ac.uk
 	HTTP/1.0 400 Wrong Protocol
 	MIME-Version: 1.0
 	Content-Type: text/html
 	<HEAD><TITLE>Hyper-G W3 Gateway V 2.51: Error</TITLE></HEAD>
 	<H1>Bad Request</H1><P>
 	The request was 'GET /home;sk=17062E7B HTTP/1.1'.

Henrik Frystyk Nielsen,
@(#) $Id: Conformance.html,v 1.5 1997/08/09 17:55:33 fillault Exp $