title: How to use no_proxy on Linux machines - wildcards, leading dots
body: <p>I am puzzled by the <code>no_proxy</code> environment variable on Linux.</p>
  <p>There are many instructions on the internet that show leading dots for example <code>.localdomain.com</code> <a href="https://stackoverflow.com/a/19719875/202576">https://stackoverflow.com/a/19719875/202576</a></p>
  <pre><code>export no_proxy=&quot;localhost,127.0.0.1,localaddress,.localdomain.com&quot;
  </code></pre>
  <p>This example is used in relation to using <code>wget</code>. I can't however confirm that this works. For example on Ubuntu 18.04 I have remove the leading dot to get it to work. Note I am using a sub domain for example <code>wget mysite.localdomain.com</code>.</p>
  <pre><code>export no_proxy=&quot;localhost,127.0.0.1,localaddress,localdomain.com&quot;
  </code></pre>
  <p>When I use a <code>curl</code> it will work with a leading dot.</p>
  <p>So it seems that the way <code>no_proxy</code> should be configured depends on the tool? It is different for <code>curl</code> and <code>wget</code>.</p>
  <p>Is there a convention for <code>no_proxy</code> that will work for all tools?</p>
  <p>I suppose writing out each and every full domain name will work.</p>