Re: plain text protocol [was: Re: Performance analysis questions]
Andrew Payne <payne@n8kei.tiac.net>
Errors-To: listmaster@www0.cern.ch
Date: Sun, 5 Jun 1994 04:42:36 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <199406041614.MAA02288@n8kei.tiac.net>
Errors-To: listmaster@www0.cern.ch
Reply-To: payne@n8kei.tiac.net
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Andrew Payne <payne@n8kei.tiac.net>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: plain text protocol [was: Re: Performance analysis questions]
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Rick Troth writes:
>> Suppose, in the future, we want to be able to take the md5 checksum of
>> the HTTP headers. If you corrupt the bytes by throwing away whitespace
>> at the end of a line, you defeat such efforts.
>
> You're saying that HTTP is -not- a plain text protocol.
> If it's not a plain text protocol, then GET should have been
>something like (in C):
>
> sprintf(GET_REQUEST,"%c%s",0x01,URL)
What is a "plain text protocol"? If you answer, please be very, very
precise.
HTTP depends on reliable, 8-bit transport. The fact that HTTP has byte
sequences that spell out English words has no implication on other aspects
of the protocol.
-andy