BlogsGitLabProxy Environment Variable Standardization

Proxy Environment Variable Standardization

Proxy Environment Variable Standardization

1
posts
2021

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.

2021

We need to talk: Can we standardize NO_PROXY?

1/27/2021

This post details the historical evolution of proxy environment variables (`http_proxy`, `https_proxy`, `no_proxy`) and their inconsistent implementations across various languages and tools (curl, wget, Ruby, Python, Go, Java). It highlights the differences in handling case sensitivity, suffix matching, wildcard support, CIDR blocks, and IP address resolution within `no_proxy`. The post also discusses a real-world customer issue caused by these discrepancies, emphasizing the need for standardization.