{"action":"opened","issue":{"url":"https://api.github.com/repos/fixerAPI/fixer/issues/119","repository_url":"https://api.github.com/repos/fixerAPI/fixer","labels_url":"https://api.github.com/repos/fixerAPI/fixer/issues/119/labels{/name}","comments_url":"https://api.github.com/repos/fixerAPI/fixer/issues/119/comments","events_url":"https://api.github.com/repos/fixerAPI/fixer/issues/119/events","html_url":"https://github.com/fixerAPI/fixer/issues/119","id":462708779,"node_id":"MDU6SXNzdWU0NjI3MDg3Nzk=","number":119,"title":"dropped HTTPS support for legacy","user":{"login":"gingerlime","id":524274,"node_id":"MDQ6VXNlcjUyNDI3NA==","avatar_url":"https://avatars2.githubusercontent.com/u/524274?v=4","gravatar_id":"","url":"https://api.github.com/users/gingerlime","html_url":"https://github.com/gingerlime","followers_url":"https://api.github.com/users/gingerlime/followers","following_url":"https://api.github.com/users/gingerlime/following{/other_user}","gists_url":"https://api.github.com/users/gingerlime/gists{/gist_id}","starred_url":"https://api.github.com/users/gingerlime/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gingerlime/subscriptions","organizations_url":"https://api.github.com/users/gingerlime/orgs","repos_url":"https://api.github.com/users/gingerlime/repos","events_url":"https://api.github.com/users/gingerlime/events{/privacy}","received_events_url":"https://api.github.com/users/gingerlime/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-07-01T13:16:03Z","updated_at":"2019-07-01T13:16:03Z","closed_at":null,"author_association":"NONE","body":"We're suddenly seeing these (hidden) errors from fixer\r\n\r\n```ruby\r\nirb(main):001:0>     response = RestClient.get(\r\nirb(main):002:1*       \"https://data.fixer.io/api/latest\",\r\nirb(main):003:1*       :params => {:base => \"USD\", :access_key => fixer_api_key}\r\nirb(main):004:1>     )\r\n=> <RestClient::Response 200 \"{\\\"success\\\":...\">\r\nirb(main):005:0> JSON.parse(response)\r\n=> {\"success\"=>false, \"error\"=>{\"code\"=>105, \"type\"=>\"https_access_restricted\", \"info\"=>\"Access Restricted - Your current Subscription Plan does not support HTTPS Encryption.\"}}\r\n```\r\n\r\nWe're on the free legacy plan ... We can switch to HTTP obviously. Those conversion rates are not really a secret, but our api key kinda is, isn't it? Are you actually encouraging people to leak their own API keys to your system??\r\n\r\nWe don't have a problem paying for a good service (in fact, I upgraded to a paid account), but this feels a bit like bait-and-switch, I have to say... Especially since you guys dropped the open API a while back which also caused us issues until we signed for the legacy account. So it's not the first time :-/\r\n\r\nReturning an error inside a 200 seems also a bit weird and I was lucky to debug this by chance and find out it was doing this... "}}
{"actor":{"display_login":"gingerlime"}}