Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • Support Team Meta Support Team Meta
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 365
    • Issues 365
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Support TeamGitLab Support Team
  • Support Team MetaSupport Team Meta
  • Issues
  • #2991
Closed
Open
Issue created Dec 13, 2020 by Nourdin el Bacha@nelbachaMaintainer

Research how `*_proxy` environment variables are used in various tools

This issue's purpose is for me to gather the most important bits of information regarding *_proxy usage in various tools and languages.

Update:

So far I've researched Curl, Wget, Golang and Ruby.
These by themselves demonstrate the inconsistency with regards to using *_proxy through environment variables.

As such, the only conclusion I can draw at the time of writing is to always provide the lowercase and uppercase variant, and to ensure that its values are not different due to precedence differences.

Edited Dec 15, 2020 by Nourdin el Bacha
Assignee
Assign to
Time tracking