W3C home > Mailing lists > Public > www-lib@w3.org > July to September 1995

Re: Encoding the form-urlencoded Media Type

From: Henrik Frystyk Nielsen <frystyk@w3.org>
Date: Thu, 17 Aug 1995 15:24:35 -0400
Message-Id: <9508171924.AA08905@www20>
To: "Daniel W. Connolly" <connolly@beach.w3.org>
Cc: html-wg@oclc.org, www-lib@w3.org

> >  Looking at the just-
> >released-to-the-public W3C WWWLibrary, HTEscape.c appears to let
> >"-._" pass unencoded, but not the "safe" `$'; the "extra" `*' is
> >O.K., yet none of its peers are.
> 
> This is a defect in WWWLibrary. I believe henrik already knows
> about this. I'll copy www-lib@w3.org on this just in case.

I do - I use half of my time updating the code according to I don't know how 
many specificatins :-( The escape/unescape is one of the places where there 
still are problems.

> >I think we're all in agreement that alphanumerics don't need to
> >be encoded.  Nowhere else in draft-ietf-html-spec-05.txt is
> >there any mention of what constitute "reserved characters," but
> >it seems that [URL]'s definition isn't applicable,
> 
> Why not? I believe [URL]'s definition is applicable. Hmmm...
> it may be updated by [RELURL]. Roy?
>
> > yet the
> >reference implementation doesn't limit itself to strict
> >alphanumerics either.

It will be fixed in the next release

-- 

Henrik Frystyk Nielsen, <frystyk@w3.org>
World-Wide Web Consortium, MIT/LCS NE43-356
545 Technology Square, Cambridge MA 02139, USA
Received on Thursday, 17 August 1995 15:24:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:25 GMT