# Chef-client && no\_proxy

**URL:** <https://discourse.chef.io/t/chef-client-no-proxy/6502>\
**Category:** Chef Infra (archive)\
**Created:** [April 20, 2015, 9:28pm UTC](https://discourse.chef.io/t/chef-client-no-proxy/6502 "2015-04-20T21:28:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Morgan\_Blackthorne](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/morgan_blackthorne/32/100_2.png) [@Morgan\_Blackthorne](https://discourse.chef.io/u/Morgan_Blackthorne)\
**Post date:** [April 20, 2015, 9:28pm UTC](https://discourse.chef.io/t/chef-client-no-proxy/6502/1 "2015-04-20T21:28:30Z")

</div>

So I recently made a change to our chef-client settings so that we specify  
that our chef server, [chef.trstone.com](http://chef.trstone.com), is set as no\_proxy. However, even  
after setting that, one of our users is seeing this output:

38947 ==\> default: [2015-04-16T21:52:14+00:00] DEBUG: Chef::HTTP  
calling Chef::HTTP::ValidateContentLength#handle\_request  
38948 ==\> default: [2015-04-16T21:52:14+00:00] DEBUG: Using  
ashproxy.lan.flt:3128 for proxy  
38949 ==\> default: [2015-04-16T21:52:14+00:00] DEBUG: Initiating GET  
to [https://chef.trstone.com/organizations/homeslice/nodes/kburnett-vagrant](https://chef.trstone.com/organizations/homeslice/nodes/kburnett-vagrant)

I am assuming that that log message simply indicates what was being  
referenced via http\_proxy and https\_proxy. Is there a way to confirm that  
chef-client is not using that proxy server to talk to the Chef server?

I mean, I’m pretty sure it’s working, by looking at the access.log on the  
squid boxes, but being able to confirm it from the perspective of  
chef-client itself would be a good thing.

Thanks.

–  
~_~ StormeRider ~_~

“Every world needs its heroes […] They inspire us to be better than we  
are. And they protect from the darkness that’s just around the corner.”

(from Smallville Season 6x1: “Zod”)

On why I hate the phrase “that’s so lame”… [http://bit.ly/Ps3uSS](http://bit.ly/Ps3uSS)