Re: Cache woes.
Date: Fri, 20 May 1994 16:42:17 +0200
Message-id: <>
Precedence: bulk
To: Multiple recipients of list <>
Subject: Re: Cache woes.
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset=US-ASCII
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL21]
X-Mailer: ELM [version 2.4 PL21]
Dan Connolley wrote:
@ It is also safe to change:
@        GET HTTP/1.0
@ to
@        GET HTTP/1.0
@ though it is NOT safe to mess with /, ?, ;, or = chars.

And Ari Luotonen wrote.
@ It should be safe; however, as you can see from httpd 3.0pre5 release
@ notes, it was indeed causing problems with bad servers which expect
@ legal characters to be escaped, or vice versa.  So in other words, pre5
@ and later don't do it anymore.

Hrm, okay, so in the future it should be okay. The cache in question was
a CERN one, no idea what version, that was translating '=' to %3D which
as Dan said is erm "NOT safe". That was the only thing I could see
causing problems (BTW from what I am told - not had a chance to check -
the BNF says that = should be escaped. Is that right?)

If Ari wants I can find out which version...


| Computer Centre, Brunel University, Uxbridge, Middx., UB8 3PH, ENGLAND. |
|___VOICE:_+44_895_274000_extn_2391_______EMAIL: __|
|                           |