#562: cabal-install update fails going through a HTTP proxy (but not consistently) ----------------------------+----------------------------------------------- Reporter: acid2 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Resolution: Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Comment (by duncan): Difference: In failing case {{{ X-Cache: HIT from wwwcache.lancs.ac.uk X-Cache-Lookup: HIT from wwwcache.lancs.ac.uk:8080 X-Cache: MISS from wwwcache.lancs.ac.uk X-Cache-Lookup: MISS from wwwcache.lancs.ac.uk:8080 Via: 1.0 wwwcache3.lancs.ac.uk:8080 (squid/2.6.STABLE22), 1.0 wwwcache1.lancs.ac.uk:8080 (squid/2.7.STABLE4) Connection: close }}} In the working case {{{ X-Cache: HIT from wwwcache.lancs.ac.uk X-Cache-Lookup: HIT from wwwcache.lancs.ac.uk:8080 Via: 1.0 wwwcache3.lancs.ac.uk:8080 (squid/2.6.STABLE22) Proxy-Connection: close }}} In particular in the failing case we get a cache hit followed by a mystery miss and finally `Connection: close`. In the working case we get no miss and a `Proxy-Connection: close`. Why `Connection:` vs `Proxy-Connection:` we wonder, and what is this cache miss about? -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/562#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects