Re: Imcompatible HTTP/1.0 on different severs

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: David C. Martin: "saving URL's"
• Previous message: Roy Smith: "Re: Anchors in current file..."

Date: Thu, 15 Jul 1993 16:19:37 -0700 (PDT)
From: "Tony Johnson (415) 926 2278" <TONYJ@scs.slac.stanford.edu>
Subject: Re: Imcompatible HTTP/1.0 on different severs
To: timbl@nxoc01.cern.ch
Cc: www-talk@nxoc01.cern.ch
Message-id: <01H0KT26FN9GB9SIUS@SCS.SLAC.STANFORD.EDU>
X-Envelope-To: timbl@nxoc01.CERN.CH, www-talk@nxoc01.CERN.CH
X-Vms-To: IN%"timbl@nxoc01.CERN.CH"
X-Vms-Cc: TONYJ, IN%"www-talk@nxoc01.CERN.CH"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Status: RO

>Tim

>>   b) (e.g: the CERN server) return the requested document with no  
>>      header. 
>
>
>	This is a deliberate bug introduced by the -DXMOSAIC_HACK
>	option in the libwww.  It is put in because otherwise
>	XMosaic would not be able to read anything except for
>	plain text and HTML. The MOMENT that mosaic uses HTTP2
>	then all servers should turn off this hack! 

I don't quite follow the logic here. Why does the hack to support HTTP/0.9
for mosaic have to affect the behaviour of the server when a HTTP/1.0 client
is trying to connect. This makes it very hard to try out HTTP/1.0 now, and will
also make it difficult for mosaic when it does support HTTP/1.0, unless all
servers are instantaneously upgraded.

If the hack is changed to affect only the HTTP/0.9 protocol now, then the 
transition to HTTP/1.0 will be easy and not involve any instantaneous upgrades
in the future.

Or have I missed something here??

Tony Johnson