413 error while authenticating with omniauth-twitter when this gem is in the bundle about active_paypal_adaptive_payment HOT 8 CLOSED

Hey, thanks for setting the repo!

Can you try to see what happen if you add the following to your config/environments/development.rb

App::Application.configure do
  config.setting...
end
ActiveMerchant::Billing::Base.mode = :test

from active_paypal_adaptive_payment.

The error persists after adding the line.
BTW, I've reproduced the bug in production env (is the same bug present in http://catarse-test.herokuapp.com/auth/twitter)

from active_paypal_adaptive_payment.

I was able to recreate the error, but that 413 is kind of cryptic error :( Are you still having the issue?

from active_paypal_adaptive_payment.

Yeah, I had to remove the gem to keep using the twitter authentication.

On Tue, Jul 3, 2012 at 9:16 AM, Jose Pablo Barrantes <
[email protected]

wrote:

I was able to recreate the error, but that 413 is kind of cryptic error :(
Are you still having the issue?

---

Reply to this email directly or view it on GitHub:

#26 (comment)

from active_paypal_adaptive_payment.

I had to patch oauth-ruby in order to both active_paypal_adaptive_payment and omniauth-twitter work in my project:
https://github.com/dmitriybudnik/oauth-ruby/commit/4731a822431f838019b9dfca787cf9f97eee3d3a#L0R338

from active_paypal_adaptive_payment.

@dmitriybudnik thanks for letting us know! 🤘

from active_paypal_adaptive_payment.

I've nailed it down to be caused by monkey-patching Net::HTTPHeader#[]= here:
https://github.com/jpablobr/active_paypal_adaptive_payment/blob/master/lib/active_merchant/billing/gateways/paypal_adaptive_payments/ext.rb#L32-42
it just strips down-casing of header-name out off original method:
https://github.com/ruby/ruby/blob/70271340af90bdfedd52854b45704cb488946d92/lib/net/http.rb#L1160-1166
Why it's there?

from active_paypal_adaptive_payment.

@dmitriybudnik to be honest I don't remember and I'm actually not working with this gem any more...

That said :/, I guess it has something to do with the way PayPal validates headers... they always come with weird sh*t! But it might very well be that they change it and the downcase hack is not be needed any more.

Would you be able to test that? if so, and if it works... I'll be more than happy to accept a pull request.

Many thanks for your debugging efforts! :)

from active_paypal_adaptive_payment.