Skip to content

dropped HTTPS support for legacy #119

@gingerlime

Description

@gingerlime

We're suddenly seeing these (hidden) errors from fixer

irb(main):001:0>     response = RestClient.get(
irb(main):002:1*       "https://data.fixer.io/api/latest",
irb(main):003:1*       :params => {:base => "USD", :access_key => fixer_api_key}
irb(main):004:1>     )
=> <RestClient::Response 200 "{\"success\":...">
irb(main):005:0> JSON.parse(response)
=> {"success"=>false, "error"=>{"code"=>105, "type"=>"https_access_restricted", "info"=>"Access Restricted - Your current Subscription Plan does not support HTTPS Encryption."}}

We'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??

We 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 :-/

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions