Support SSL proxy connections for package management
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to use racket 6.12 on Windows 7 x64. I get the following error message when I try to update the packages:
tcp-connect: connection failed
address: download.racket-lang.org
port number: 443
system error: No connection could be made because the target machine actively refused it.; errid=10061
I found https://www.reddit.com/r/Racket/comments/6jsqmg/racket_behind_a_proxy/ describing the same or a very similiar problem. Like in that post, I have also set multiple environment variables like HTTP_PROXY that I use successfully with other tools.
Is there anything else I can do to get this working? Or is it really an unimplemented feature? If so, how can I help implement it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by locating the package-management update entry point and checking how HTTP_PROXY and related environment variables are handled during the failed TLS connection. Done means package updates work through an SSL proxy on the reported Windows setup, with coverage for the proxy behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100