Re: Seeming bug in URI::URL
Aaron Sherman (ajs@openmarket.com)
Mon, 16 Oct 1995 12:50:01 -0400
I don't understand what a "form info encoding in query" is, but the
library, as it stands, needs to not DECODE things like & because they
are ambiguous after decoding (eg. a=%26b&c=d becomes a=&b&c=d when
decoded, and unless the string carries some kind of state with it,
this is now a different query).
However, once you do that, you run into encoding having to be smart
and look at what follows a %-sign when ENCODING, because there are now
two cases:
1. An escaped character which should not be re-escaped.
2. A %-sign embedded into the string, which should be escaped.
This makes encoding much slower and messier.
Any ideas?
-AJS
--
Aaron Sherman <ajs@ajs.com> B4 f w+ c kv s+(--)v r p
I-Kinetics, Inc. Pager: (508)545-0584
1 NE Executive Park Fax: (617)270-4979
Burlington, MA 01803-5005 WWW: http://ajs.com/~ajs/
ajs@ajs.com or ajs@openmarket.com
"I speak for no one."