Hello, On Sat, 11 Dec 2010 19:10:45 +0100 (CET) Daniel Stenberg <[email protected]> wrote:
> I'm sorry but I'm completely missing the point here. > What are you suggesting (lib)curl should do and when? HTML4 standard says: > Space characters are replaced by > `+', and then reserved characters are escaped as described in RFC1738, > section 2.2: Non-alphanumeric characters are replaced by `%HH', a > percent sign and two hexadecimal digits representing the ASCII code of > the character. Line breaks are represented as "CR LF" pairs (i.e., > `%0D%0A'). I think the beast way would be making a "curl option" that enables either RFC1738 or urlencode, that means at least adds space replacement (not sure if that's enough, please check both documents). Or, you may add two functions to the API to perform this way of encoding. Alternatively, if you don't want to do either, just mention it in the docs. -- WBR, Andrew
signature.asc
Description: PGP signature
