<p>While working in a restricted on-prem network, popular package managers like Composer or NPM may not properly work. Thanks to the proxy filtering technologies at the internet gateway end.</p>
<p>These package managers often download files over an unencrypted HTTP connection and verify the binaries using a checksum or GPG signature. However, in some cases, it is possible to bypass the filtering by enforcing HTTPS so these tools use an encrypted connection to fetch and download artifacts.</p>
<h3 id="heading-composer">Composer</h3>
<pre><code class="lang-bash">composer config --global disable-tls
composer config --global secure-http
</code></pre>
<h3 id="heading-npm">NPM</h3>
<pre><code class="lang-bash">npm config <span class="hljs-built_in">set</span> registry https://registry.npmjs.org/
npm config <span class="hljs-built_in">set</span> ssl-strict=<span class="hljs-literal">false</span>
</code></pre>
<h3 id="heading-apt">Apt</h3>
<pre><code class="lang-bash">sed -i s/http/https/g /etc/apt/sources.list
</code></pre>


While working in a restricted on-prem network, popular package managers like Composer or NPM may not properly work. Thanks to the proxy filtering technologies at the internet gateway end.

These package managers often download files over an unencrypted HTTP connection and verify the binaries using a checksum or GPG signature. However, in some cases, it is possible to bypass the filtering by enforcing HTTPS so these tools use an encrypted connection to fetch and download artifacts.

### Composer

```bash
composer config --global disable-tls
composer config --global secure-http
```

### NPM

```bash
npm config set registry https://registry.npmjs.org/
npm config set ssl-strict=false
```

### Apt

```bash
sed -i s/http/https/g /etc/apt/sources.list
```

Minhaz's Blog

Minhaz's Blog

Bypass Proxy for Composer/NPM/Apt

Composer

NPM

Apt