Jira (PUP-9316) implement no_proxy in puppet.conf

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on PUP-9316   Re: implement no_proxy in puppet.conf Elof Ofel In 5.5.16 and prior, puppet claimed to observe the no_proxy environment variable, but it didn't actually do that, because the connection factory called Puppet::Util::HttpProxy.no_proxy?(Site) passing a site instance instead of a String or URI. The reason this wasn't noticed before is because the no_proxy? silently rescues URI::InvalidURIError and returns false. This was fixed in puppet 5.5.17 in commit cb4a9b7da148f97ed9ce02f859ad6a90115c0079. As a result, puppet now correctly observes the no_proxy environment variable. Since your no_proxy environment variable doesn't include your puppetserver, puppet is trying to use the proxy. You'll want to add your puppetserver FQDN to the no_proxy environment variable. However, there are 2 other issues to be aware of: PUP-9990 - Puppet could end up using a proxy even though it matched the no_proxy exception list. This was due to Puppet incorrectly creating the Net::HTTP object when running with ruby 2 and up. It was fixed in 54a3e6bfe1f907bbe5505b39f4d9cdfec2be428f, but needs to be backported to 5.5.x. I've filed that as PUP-10112. PUP-10106 - Puppet and ruby interpret the no_proxy environment variable differently when specifying a domain. Puppet accepts *.example.com and .example.com, whereas ruby only accepts example.com. Both of these issues can be avoided by specifying the FQDN of the puppetserver in the no_proxy environment variable. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.285347.1542320475000.6505.1571956021280%40Atlassian.JIRA.