/Proxy-DEFUSAL-KIT

ENSIAS Proxy : TOUT-EN-UN

ENSIAS Proxy : TOUT-EN-UN

We all can admit that the poxy is a pain in the 🍑
After only one year in ENSIAS, just seeing "10.23.201.11:3128" make me want to throw out.

Pardon my French

YOU SUCK

YES you do, now bookmark this so you wont anymore hehe !

This is a collection of all the proxy commands i needed to get around it, contributions are very welcome to make this a reference.

  1. Windows
  2. Debian
  3. FEDORA / CENTOS
  4. NPM
  5. GIT family
  6. Gradle
  7. DOCKER

WINDOWS:

  • SETTING :
set http_proxy=10.23.201.11:3128
set https_proxy=10.23.201.11:3128
  • UNSETTING :
set http_proxy=
set https_proxy=
  • Check proxy status
netsh winhttp show proxy

Debian :

  • SETTING :
export {http,https,ftp}_proxy="http://10.23.201.11:3128"
export {HTTP,HTTPS,FTP}_PROXY="http://10.23.201.11:3128"
  • UNSETTING :
unset {http,https,ftp}_proxy
unset {HTTP,HTTPS,FTP}_PROXY
  • CHECK STATUS :
echo $http_proxy
echo $https_proxy

FEDORA / CENTOS :

  • SETTING :
export http_proxy=http://10.23.201.11:3128
  • Without SHELL :
echo "http_proxy=http://10.23.201.11:3128/" > /etc/environment
  • With SHELL
echo "export http_proxy=http://10.23.201.11:3128/" > /etc/profile.d/http_proxy.sh \with SHELL
  • Other programms (YUM) :
echo "proxy=http://10.23.201.11:3128" > /etc/yum.conf
  • UNSETTING :
unset http_proxy
http_proxy=""
  • CHECK STATUS :
echo $http_proxy
cat /etc/yum.conf

NPM / NODEJS :

  • SETTING :

PS: use sudo if necessary

npm config set proxy http://10.23.201.11:3128 -g
npm config set https-proxy http://10.23.201.11:3128 -g
npm config set registry http://registry.npm.taobao.org -g

Unfortunately, Node does not include a mechanism for global proxy settings. It seems that proxy information must be set on each call to http.request (the only solution i found) The global-tunnel-ng module on NPM appears to handle this:

var globalTunnel = require('global-tunnel-ng');

globalTunnel.initialize({
host: '10.23.201.11',
port: 3128,
proxyAuth: 'userId:password', // optional 
sockets: 50 // pool size for each http and https
});

After the global settings are establish with a call to initialize, both http.request and the request library will use the proxy information. Lemme know you solutions !

  • UNSETTING :
npm config rm proxy
npm config rm https-proxy
  • CHECK STATUS :
npm get https-proxy
npm get proxy

GIT :

  • SETTING :
git config --global http.proxy http://10.23.201.11:3128
git config --global https.proxy https://10.23.201.11:3128
  • UNSETTING :
git config --global --unset http.proxy
git config --global --unset https.proxy
  • CHECK STATUS :
git config --global --get http.proxy

GRADLE :

  • SETTING :
export GRADLE_OPTS=-Dhttp.proxyHost=http://10.23.201.11 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=http://10.23.201.11 -Dhttps.proxyPort=3128
  • UNSETTING :
unset GRADLE_OPTS
  • CHECK STATUS :
echo $GRADLE_OPTS

DOCKER :

  • SETTING :
sudo systemctl start docker
vi /etc/sysconfig/docker
HTTP_PROXY="http://10.23.201.11:3128"
HTTPS_PROXY="https://10.23.201.11:3128"
systemctl daemon-reload
systemctl docker restart
  • UNSETTING :
vi /etc/sysconfig/docker
HTTP_PROXY=""
HTTPS_PROXY=""
systemctl daemon-reload
systemctl docker restart
  • MISC:

A very good read :
https://elegantinfrastructure.com/docker/ultimate-guide-to-docker-http-proxy-configuration/