Date: Wed, 5 Oct 1994 11:15:17 +0100
Message-Id: <9410051015.AA23419@neon.mcom.com>
From: luotonen@neon.mcom.com (Ari Luotonen)
To: Multiple recipients of list <www-proxy@www0.cern.ch>
Subject: Re: Behavioural problem of cache/proxy (latest version)
> I probably should be sending this one direct to cern but I thought that
> its probably a bit more widespread than that.
>
> Its another FORM problem :)
>
> I have a FORM that basically spits out the URL:
>
> http://echo.brunel.ac.uk:4040/path=<a_ufn_to_dn_path>?ufn=<ufn>
>
> However by the time it has passed through the cache/proxy it ends up as:
>
> http://..../path%3D......?ufn%3D....
>
> I remember talking at length to Ari about this one. As I recall he came
> down on my side saying that the proxy really shouldnt alter the URL on
> the way through. At least not escape it any more than it was. Looking at
> the HTTP/HTML specs, I cant see '=' listed as a char that should be
> escaped (space, +, '/' in a FORM, <CR>, <LF>, etc are listed) but I cant
> find a more recent than Nov 1993 listing :)
You are absolutely right about this, and I *did* fix it, and I'm 100%
sure about it. I just checked my last version 3.0pre6, and it worked
fine, and then the newest one 3.0, and noticed that it was indeed
broken again... :-( So with pre6 it works as you describe and as it
should. I suppose when they've cleaned up the libwww they've by
mistake removed the special case that made sure that the URI was
passed on exactly as it came in.
Cheers,
-- Ari Luotonen Mosaic Communications Corp. 650 Castro Street, Suite 500 Mountain View, CA 94041, USA