The URL must be encoded because may have illegal characters: The user may enter an URL like: http://www.site.com/fol 1/fol 2/file 1.jpg?par=sdf|dfgó.jpg
This URL must be encoded as: http://www.site.com/fol%201/fol%202/file%201.jpg?par=sdf%7Cdfg%F3.jpg This kind of codification must be "parse-sensitive", because an URL cannot be completely encoded without taking care of Protocol, Address, Port, Folders, File and Parameters (..and Authentication and Bookmark information). ---- Original Message ----- From: "Nicholas Sherlock" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Sunday, February 12, 2006 11:42 PM Subject: Re: [twsocket] Encode URL > David A. G. wrote: >> Thanks DZ-Jay. I think we need to add a more complete function, ..just >> what >> to do if we need to encode (correctly) a full URL to use with HttpCli? >> ...It >> was my problem the last week!! >> > That would make no sense. The encoder couldn't tell the difference > between real elements that provide the structure of the URL, and > elements that should actually be escaped as they don't form part of the > structure. What would be the point in encoding an entered URL? > > Cheers, > Nicholas Sherlock > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
