Yes, originally I was not allowing BEAST, but allowing it did not make
any difference. Since yesterday,
I have put in code to retry the POST if I get that failure, and about
half of the time it will get through.
On 11/14/2013 4:02 PM, Nick Zitzmann wrote:
On Nov 13, 2013, at 11:22 PM, Jeff McKay <[email protected]> wrote:
Using this exactly same program to connect to a private server running Exchange
2013 (over the internet ) works just
fine. For all the world this looks to me like some problem with Microsoft's
Office 365 servers, but I need to do something
to work around it. Any ideas on settings I can use to fix this?
Does it help if you disable the BEAST workaround (set CURLOPT_SSL_OPTIONS to
CURLSSLOPT_ALLOW_BEAST)?
Nick Zitzmann
<http://www.chronosnet.com/>
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
