Jingkai He comments

Results 3 comments of


                                            Jingkai He

Using application/x-www-form-urlencoded as the default request content type when getting access_token

@sferik Tested using Ruby 1.8.7 against master branch locally. Got exact the same fail. Presumably something is broken. ``` log vagrant@localhost:/vagrant/omniauth-oauth$ git rev-parse HEAD 9f4a4f136c46eec96cb1e7f970200647e6a49b29 vagrant@localhost:/vagrant/omniauth-oauth$ ruby -v ruby 1.8.7...

Using application/x-www-form-urlencoded as the default request content type when getting access_token

I believe that there's a problem with `Hashie::Mash`, (since I notice [extra cannot be assigned to the hash](https://github.com/intridea/omniauth/blob/c3e3aa5bbfb589db1ebed40324c7eea2e3153f8c/lib/omniauth/strategy.rb#L336)) ``` ruby vagrant@localhost:/vagrant/omniauth-oauth$ ruby -v ruby 1.8.7 (2013-12-22 patchlevel 375) [x86_64-linux] vagrant@localhost:/vagrant/omniauth-oauth$...

chef_user and chef_org load_current_value into node.run_state is not working

Running into the same issue @nicutor it appear to be an issue that exists in 2.3.2 - https://github.com/chef-cookbooks/chef-ingredient/blob/v2.3.2/resources/chef_org.rb#L55-L62 should be addressed in the future release though - https://github.com/chef-cookbooks/chef-ingredient/pull/233