Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • lemonldap-ng lemonldap-ng
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LemonLDAP NGLemonLDAP NG
  • lemonldap-nglemonldap-ng
  • Issues
  • #2715
Closed
Open
Issue created Feb 28, 2022 by Maxime Besson@maxbes🔧Maintainer

http_proxy env variable not used by the manager

Concerned version

Version: 2.0.14

Summary

Our documentation states

If the LL::NG server needs a proxy for outgoing connections, then you need to configure some environment variables.

However LWP::UserAgent::env_proxy is only set in some Portal modules, not in the manager or handler

Possible fixes

  • Why is env_proxy not set globally? Is it because of handler REST/devops calls?
  • We should at least enable env_proxy in the manager or globally in the portal (Auth::REST does not use it by default)
  • What about calling reloadUrls
  • We could document the fact that PERL_LWP_ENV_PROXY=1 makes LWP use http_proxy globally
Edited Mar 03, 2022 by Maxime Besson
Assignee
Assign to
Time tracking