Add on to my initial question... here's the error I receive using C++ & PocketSOAP: HttpTransport: Failed to send soap request: <COM> Source = PocketHTTP ...
well, you're missing the code that creates the envelope and calls send, but if you getting Failed during SSL handshake (and the AV sounds like a red herring,...
Hi Simon, I see on the release notes for HTTP 1.1 that problems with SSL and PocketPC 2003 were resolved in this release. We'll upgrade our release and...
Simon, We are using pockethttp to talk to Authorize.net using ssl. ... During the week of March 16 - 20, 2009, Authorize.Net will be deprecating all legacy...
... with the ... PocketXML-RPC and it'll use the ... Sounds good, Can I get a copy of the latest Pocket HTTP source or binary from somewhere, the latest one I...
... I decided to format the post data manually, and it works a treat. myURL = "http://www.blah.com" boundary = "__pockethttp_post_boundary__" set req =...
... PocketHTTP uses the underlying OS supplied crypto support to do SSL, so you should automatically negociate the best crypto level supported between the...
I would guess that the SSE config doesn't allow basic auth, while the MOSS SW did, can you change the SSE setup to allow basic auth (it is using IIS?) Cheers ...
Hi, apologies for what may be a very "newbie" question, but it's got my curiousity going. I want to use PocketSOAP to generate multiple VBScripts I can reuse...
I'm having some problems at some of my clients and sometimes I need to use the header "Expect: 100-continue". I already did this for C# and C++ but I'm having...
Are you really sure this is your problem? i've never seen a .NET server that requires the requests to use a Expect: 100-continue header. The http request...
Hi Simon all I know about it currently is it's a customer's in-house "implementation of .NET framework", and I suspect a "vanilla"/Visual Studio-generated...
PocketSOAP works fine with .NET, i've used it with many .NET services. Most problems revolve around namespaces, see http://www.pocketsoap.com/faq/#dotnetdoclit...
Hi Simon I must be missing something really obvious - when I put the " e.encodingStyle="" " and "e.URI" statements in as per the FAQ I still get the XI:Type...
it doesn't suppress the xi;types. Most .NET interop problems are around using doc/lit instead of rpc/enc, which is what that faq entry is about. I'm not aware...
For a new project I'm looking for a freelance programmer that can write some code for us in VB6 + pocketsoap to download info from a webservice. If anyone is...