ProxymanApp / ProxymanApp/Proxyman

Terminal CLI requests not shown, even if HTTP_PROXY is set

Open
#506 6 comments 1 reaction 1 assignee View on GitHub

@NghiaTranUIT is already working on this.

Since May 19, 2020.

✅ Done bug Discussion
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Proxyman version? (Ex. Proxyman 1.4.3)

1.23.0

macOS Version? (Ex. mac 10.14)

10.15.4

Steps to reproduce
  1. Open Terminal
  2. Set HTTP_PROXY environment variable
  3. Check output from env to confirm environment is set correctly
  4. Run a command-line tool that makes an HTTP request (e.g., tabix)

As an example command:

$ HTTP_PROXY=http://127.0.0.1:9090 
$ env | grep HTTP_PROXY
HTTP_PROXY=http://127.0.0.1:9090
$ tabix http://explore.altius.org/tabix/vA/hg19.15.all.KL.gz chr5:78459198-78643943
...

Other tools also do not seem to work (e.g. curl):

$ HTTP_PROXY=http://127.0.0.1:9090 curl http://explore.altius.org/tabix/vA/hg19.15.all.KL.gz.tbi -o /tmp/foo.tbi

I do know that one can manually set the proxy in curl with the -x option. However, I'm trying to demonstrate that HTTP_PROXY appears not to work with Proxyman for generic CLI operations.

Expected behavior

When HTTP_PROXY is set, I would expect to see the details of this and other HTTP requests in Proxyman made with CLI tools.

Screenshots (optional)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.