I posted this to the comm list first, but it seems no one reads that these days, so I'll ask here.
If I've got a secure server setup and running, all I should need to do is change my INetLibSockOpen to use inetSchemeHTTPS and use https: URL's instead of http: right? I've done this, but the Palm seems to take a dive off the deep end on INetLibSockReqSend causing it to read an unallocated chunk ... Now if I just use inetSchemeHTTPS but leave the URLs at http: ... this seems to make a good secure connection to Palm.Net, but the resulting connection to my server is insecure of course. So what am I doing wrong here? For reference, I can access my secure server via https:// from a web browser, so I know it's up and running. Any oddities I should be aware of? Thanks for any info. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
