TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Proxy Environment Variable Standardization

1 post · Jan 2021

What this trail covers

This feature thread tracks the evolution and standardization of proxy environment variables, specifically focusing on the inconsistencies and challenges associated with `http_proxy`, `https_proxy`, and `no_proxy` across different programming languages and tools. It aims to document the historical development, current implementations, and the impact of these variations on system behavior and troubleshooting.

All GitLab trails
  1. We need to talk: Can we standardize NO_PROXY?This post details the historical evolution of proxy environment variables (`http_proxy`, `https_proxy`, `no_proxy`) and their inconsistent implementations across various tools and languages (curl, wget, Ruby, Python, Go, Java). It highlights the case sensitivity differences, precedence rules, and varying support for features like CIDR blocks and wildcard matching in `no_proxy`. The post also discusses the impact of these discrepancies, citing a customer issue where Git pushes worked in the CLI but failed in the web UI due to these differences, particularly between Ruby and Go implementations.