Jeff Blaine

This is httpclient 2.7.1 from rubygems.

Turns out that switching from PATCH to PUT works. **However**, testing with rest-client's PATCH (https://rubygems.org/gems/rest-client/) works fine.

Turns out that switching from PATCH to PUT works. **However**, testing with rest-client's PATCH (https://rubygems.org/gems/rest-client/) works fine.

Oops. Sorry. I found a browser tab open with my comment not apparently submitted yet, so I submitted it. We've just settled on using PUT as it works for our...

Hmm. This works now with httpclient-2.8.3 ``` [@gazoo:~] $ ruby test.rb Trying to PATCH http://our-server.example.org:8000/api/v1/device/910/ [@gazoo:~] $ ```

Friendly reminder that over 4 months have passed.

@mwrock Yes. What did your `no_proxy` setting look like? As mentioned in the original issue-opening report, it is possible maybe that the documentation for `no_proxy` is incorrect. I am using...

Here's the latest case-by-case breakdown. In **all cases below**, `knife.rb` is configured as: ``` http_proxy 'http://proxy.our.org:80' https_proxy 'http://proxy.our.org:80' no_proxy '*.our.org, localhost, 127.0.0.1' ``` ChefDK 0.15.16 # Case 1 - No...

So the problem then is that `wget` and Chef compete for the `no_proxy` environment variable, each with their own differing syntax expected.

You didn't specify what version of Chef you're running. See CHANGELOG.md quoted below. I suspect you're running an old unsupported version of chef-client. ``` 4.0.0 (2020-01-02) This cookkbook now requires...