Uses closed connection from a proxy (e.g. squid2)
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 186
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
This is related to #14, which may have not been fixed properly. When using cabal update built with HTTP-4000.2.17 and using a squid2 proxy, I get cabal: does not exist. A friend of mine did some debugging and found out:
it seems that cabal does a GET http://hackage.haskell.org/packages/archive/00-index.tar.gz
squid responds with a cache hit 301 and closes the connection.
cabal tries to use pipelining and fails
it doesn't try a new connection
It does not happen with squid3, or perl’s HTTP::Proxy.
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
Start by reviewing the related issue #14 and the cabal update request flow described in this report, then reproduce the failure with HTTP-4000.2.17 through a squid2 proxy. Done means the request no longer fails when squid closes the connection after a cached 301 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100