Update POCO library.

vendor/POCO/NetSSL_Win/doc/README.txt

@@ -1,11 +1,11 @@
 About NetSSL_Win
 ================
 
-NetSSL_Win is an implementation of the POCO NetSSL library based on Windows 
+NetSSL_Win is an implementation of the POCO NetSSL library based on Windows
 Schannel. The original NetSSL implementation is based on OpenSSL and thus
 has a few OpenSSL-isms in the interface. Generally, source code based
 on NetSSL_OpenSSL can be easily ported to use NetSSL_Win. Just a few
-minor code changes are required, due to differences in the API. 
+minor code changes are required, due to differences in the API.
 These are discussed below:
 
   - Context: The Context constructor uses different arguments. While
@@ -18,7 +18,7 @@ These are discussed below:
     must be setup.
     Please refer to the header file documentation for more information.
     Furthermore, the following Context methods are not available in NetSSL_Win:
-    addChainCertificate(), disableStatelessSessionResumption(), 
+    addChainCertificate(), disableStatelessSessionResumption(),
     enableSessionCache(),flushSessionCache(),
     getSessionCacheSize(), getSessionTimeout(),
     setSessionCacheSize(), setSessionTimeout(), sslContext(),
@@ -26,7 +26,7 @@ These are discussed below:
 
   - SSLManager: The configuration properties used to configure the SSLManager
     are different from the ones used in NetSSL_OpenSSL. Please see the
-    SSLManager header file for more information. 
+    SSLManager header file for more information.
     The isFIPSEnabled() method is not available.
 
   - X509Certificate: Saving a certificate is not supported.
@@ -39,8 +39,8 @@ The test suite and samples expect a certificate/private key file named
 any.pfx, located in the current working directory. This can be changed
 by editing the testrunner.xml/TestSuite.xml configuration files.
 Alternatively, a certificate from the Windows certificate store can be used.
-A suitable self-signed certificate can be created using the Windows 
-IIS administration console, then exported to a file, and re-imported into 
+A suitable self-signed certificate can be created using the Windows
+IIS administration console, then exported to a file, and re-imported into
 the user's personal store.
 
 To create the certificate, follow these steps:
@@ -54,7 +54,7 @@ To create the certificate, follow these steps:
   6. Export the certificate by right-clicking it and chosing "Export...".
   7. In Explorer, double-click the exported certificate file (.pfx)
      to launch the Certificate Import Wizard.
-  8. Import the certificate into your personal store by 
+  8. Import the certificate into your personal store by
      selecting "Place all certificates in the following store" and
      selecting the "Personal" store in the import wizard.
 
@@ -63,7 +63,7 @@ Windows Embedded Compact
 ------------------------
 
 Windows Embedded Compact does not support the following Schannel
-features: 
+features:
   - certificate revocation checking (Context::OPT_PERFORM_REVOCATION_CHECK)
   - TLS 1.1 and 1.2 (Context::TLSV1_1_CLIENT_USE, etc.)
   - disabling weak security algorithms (Context::OPT_USE_STRONG_CRYPTO)