Yes, I see you are only using it for conversion to/from base64. Currently you have calls to CryptStringToBinaryW & CryptBinaryToStringW in asyncrt_utils.cpp to support the conversions.
Aside from HTTPS with certs, I currently didn't know how far down these (crypto) roads you plan to go - I wasn't sure that you had or hadn't made a decision with respect to preferred hooks to cryypt32.lib to the exclusion of bcrypt.lib.
As to my own use: While I see the usual goal of RESTful APIs to include open and accessible messages, there are always offenders like myself who have extra needs - and yet can't justify dropping down to SOAP (clients would hate me) - I just need to inject a little shim here or there sometimes. And I'm always on Windows 8 or Server 2012.
Aside from HTTPS with certs, I currently didn't know how far down these (crypto) roads you plan to go - I wasn't sure that you had or hadn't made a decision with respect to preferred hooks to cryypt32.lib to the exclusion of bcrypt.lib.
As to my own use: While I see the usual goal of RESTful APIs to include open and accessible messages, there are always offenders like myself who have extra needs - and yet can't justify dropping down to SOAP (clients would hate me) - I just need to inject a little shim here or there sometimes. And I'm always on Windows 8 or Server 2012.