Hello, On Mon, 27 Dec 2010 19:31:36 +0100 (CET) Daniel Stenberg <dan...@haxx.se> wrote:
> The reverse? > curl encodes the data, surely your server end needs to DECODE the > data then? Curl has both encode and decode functions. I use decode. > > Also, some libraries depend on curl to perform this operation and > > they fail to do this correctly. > Nope. libcurl doesn't provide any particular feature for sending POST > data url encoded so such a failure would be done by the application > (like curl) and not libcurl. > One could then possibly argue that libcurl's curl_easy_escape() > function that performs the URL encoding would output '+' letters, but > that's not as easily done as spaces are not always supported as '+' > but I've never seen anyone have problems with them encoded as %20 > (before). '+' MUST be supported. I need to decode it using curl. I'm unable to do this currently. Also, speaking of servers, some of them are quite picky regarding %20/+. Some algorithms require encoding the same string in the same way on both server and client, otherwise they just don't work. If server follows the standard and client doesn't, they fail communicating. Currently curl doesn't. -- WBR, Andrew
signature.asc
Description: PGP signature
