Update requirements - libcurl

[ityndall]

After days of fighting the dreaded 401 error, I finally figured out my problem and I think it would help if it was listed as a requirement. Most of you must be using this library on a windows server, as I came to discover that Linux won't work with EWS right out of the box.

It looks like alot of NTLM changes have been made to the libcurl library, so I'm not sure exactly which version fixes the problem. I think it's safe to list 7.23.0 as the required libcurl version on Linux, as that's the last version that mention any NTLM changes.

If it helps any, here is a post I made on the subject:
http://blog.ianty.com/ubuntu/exchange-web-services-ews-ntlmv2-and-linux/

[jamesiarmes]

This is a bug in Ubuntu (and possibly other Ubuntu or Debian based distributions) and has been addressed in Issue #11. You bring up an excellent point that this should be added to the documentation and I have labeled this issue appropriately to do so.

[ityndall]

I have also verified this in Fedora, and I think it will be the same in most flavors as the libraries always take awhile to make it into core.

[andreyvk]

This might help: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/675974.

[ityndall]

andreyvk, that suggest to go back to an earlier version... why would you want to do this when you can fix it by updating to the latest stable version?

[andreyvk]

It worked for me and it might appear easier for some, since they'd be dealing with packages rather than compiling from source. I do agree, however, that your solution is better. My suggestion is just an alternative, nothing more.

[brandonwamboldt]

Updating to curl 7.26.0 fixes the problem for me.

[jamesiarmes]

This has been added to the README in edbcb65 as part of #85.

[teuneboon]

Kind of a late reply. But does anyone of you know the exact change(s)/fix(es) in libcurl that affect this issue?(so not just the version, but the changes themselves)