I didn't find a good way to debug, but I had a hunch and it proved correct: libcurl didn't have any ca certs defined. I just had to recompile libcurl and point it at my ca certs file (which I pulled from curl's site), and all was well.
On Jun 13, 11:58 pm, Heath <heath.bord...@gmail.com> wrote: > I'm trying to create a twitter client for palm's native development > kit. I'm using liboauth. Currently, I'm just trying to link against > i386. I've compiled libcurl and all dependencies for i386. I only > added support for http, https, and file URLs to libcurl. When try to > GET a request token from twitter using https, I get a NULL reply. If > I use http I get a successful reply. Twitter's API says I should use > https for all oauth requests, so I assume they'll shut off http > eventually. The oauthexample.c test program runs successfully in both > GET and POST modes. However, it only uses HTTP, not HTTPS. > > Does anyone have any suggestions for how I might debug this? > > Thanks. > > -Heath -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
