currencylayer-API icon indicating copy to clipboard operation
currencylayer-API copied to clipboard

Problem with HTTPS encryption

Open DragonOsman opened this issue 6 years ago • 1 comments

I recently got a paid "Basic" plan for the API. In my code, I have to send the request to the API by creating string objects for the host, port number and target. When I tried setting the port number to 443, I got an HTTP response with nothing more than the "HTTP/1.1 200 OK" line. It's working correctly when the port number is set to 80. My web server code, where I'm doing this, is written in C++. If someone wants to it, is in this Gist: https://gist.github.com/DragonOsman/d00ea7ec3d49c128ad7789293f156a09 . I've put the port number for the request to the API for the conversion result (I'm querying the currency conversion endpoint) back to 80 for now.

DragonOsman avatar Aug 17 '18 17:08 DragonOsman

@DragonOsman The response is a 200 OK with an error message in the body that looks something like this:

{"success":false,"error":{"code":105,"info":"Access Restricted - Your current Subscription Plan does not support HTTPS Encryption."}}

This looks like it was done on purpose to force you to upgrade to the paid version.

gzog avatar Jul 25 '20 19:07 gzog