search

oesmith / puffing-billy

A rewriting web proxy for testing interactions between your browser and external sites. Works with ruby + rspec.
MIT License
656 stars 170 forks source link

puffing-billy: Request to https://... failed with error: Content-decoder error #204

Closed zedtux closed 6 years ago

zedtux commented 6 years ago

I'm trying to figure out how to test the Braintree payment gateway (and their DropIn UI) in my Rails application.

So far, I have my test passing without any saved fixture files, but then when I run it again, I have the following error in logs (and my test is failing):

puffing-billy: Request to https://api.sandbox.braintreegateway.com:443/merchants/<braintree-merchant-id>/client_api/v1/configuration?authorizationFingerprint=8e2414b70f7e776c2bed9bdbe67f304f33310a29623c8a81d0a93ad18f63378a%7Ccreated_at%3D2017-11-13T10%3A32%3A31.368242957%2B0000%26customer_id%3D255624599%26merchant_id%3D<braintree-merchant-id>%26public_key%3D<braintree-public-key>&callback=callback_json4fd4f6c4ff2f4920abd99a9c85cca184 failed with error: Content-decoder error

I did a small project which reproduces the problem: https://github.com/zedtux/cucumber-braintree.

Can you please guide me to a solution?

ronwsmith commented 6 years ago

@zedtux is this still an issue after following recent SSL changes / documentation?

zedtux commented 6 years ago

@ronwsmith what recent SSL changes / documentation?

ronwsmith commented 6 years ago

@zedtux See the referenced issue above your comment ^^

zedtux commented 6 years ago

Thank you @ronwsmith, I will check that.

ronwsmith commented 6 years ago

@zedtux Is this still an issue?

zedtux commented 6 years ago

@ronwsmith well, this issue is stale for months, and I abandoned testing thing (repo deleted since I migrated to GitLab), so it is still an issue, but I'm not looking at it anymore.

Feel free to close this issue if no one care.

ronwsmith commented 6 years ago

Thanks for letting me know! I'll close it out for now. It's still referenced by the open PR.

ronwsmith commented 5 years ago

Fixed in v2.1.0