Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Problem with HTTPS encryption #4

Open
DragonOsman opened this issue Aug 17, 2018 · 1 comment
Open

Problem with HTTPS encryption #4

DragonOsman opened this issue Aug 17, 2018 · 1 comment

Comments

@DragonOsman
Copy link

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.

@gzog
Copy link

gzog commented Jul 25, 2020

@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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants