Better error message when HTTP_PROXY is down.

Open
#84 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
networking

Research direction

Start by reproducing the failure with HTTP_PROXY set to an unavailable proxy such as localhost:3128, then inspect the HTTP package's proxy request and error-handling entry points. The work is done when a down proxy produces a helpful error message instead of the reported uninformative output.

Written by the indexing model from the issue text.

Description

Quoting https://github.com/haskell/cabal/issues/1962:

In order to avoid #1602 I upgraded HTTP to version 4000.2.17. But I noticed a new (minor) problem: If the proxy mentioned in http_proxy is down, I get

(sid)root@kirk:~# unset http_proxy
(sid)root@kirk:~#  cabal update
Downloading the latest package list from hackage.haskell.org
(sid)root@kirk:~# export http_proxy=http://localhost:3128/
(sid)root@kirk:~#  cabal update
Downloading the latest package list from hackage.haskell.org
cabal: does not exist
# now starting the proxy
(sid)root@kirk:~#  cabal update
Downloading the latest package list from hackage.haskell.org

Certainly the error message could be more helpful.

Dominant language
Haskell
Stars
186
Forks
59
PR merge metrics
No merged PRs in 30d

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.

More from haskell/HTTP

All issues in haskell/HTTP

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.