Hi,

I'm using libcurl as cornerstone to build my own twitter client application.
I've been using libcurl for about a year or so without facing any
encoding/decoding issues but twitter's signature method has made the lib
reach an boundary (my guess).

Characters - _ . and ~ should not be encoded as specification says (
http://tools.ietf.org/html/rfc3986#section-2.3)

By now I'm "patching" the result from curl_easy_escape by manually
converting back the encoded version of those characters, but I'd be
interested to know if there would be a fix for this in a new release.

Best regards!
Miguel.

-- 
"Think" is not a four-letter word.
        -- Anonymous

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-09-28