[Hackage] #622: wrong HTTP Content-Type for tar.gz files, breaking cabal-install behind some proxies.

[Hackage]

#622: wrong HTTP Content-Type for tar.gz files, breaking cabal-install behind
some proxies.
--------------------------------+-------------------------------------------
  Reporter:  guest              |        Owner:         
      Type:  enhancement        |       Status:  new    
  Priority:  normal             |    Milestone:         
 Component:  hackageDB website  |      Version:  1.6.0.1
  Severity:  normal             |   Resolution:         
  Keywords:                     |   Difficulty:  unknown
Ghcversion:                     |     Platform:         
--------------------------------+-------------------------------------------
Changes (by guest):

  * type:  defect => enhancement

Comment:

 After reading RFC 2616, it becomes clear that the proxy is buggy.

 A transparent proxy (and a virus checker ought to be one) is not allowed
 to change Content-Encoding. Even for non-transparent proxies,
 http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.5.2 says this
 about Content-Encoding, Content-Range and Content-Type:

 ''A non-transparent proxy MAY modify or add these fields to a message that
 does not include no-transform, but if it does so, it MUST add a Warning
 214 (Transformation applied) if one does not already appear in the message
 (see section 14.46).''

 There's no such warning in the reply above.

 I still think the headers should be different, but it doesn't seem to be a
 bug on the hackage side. Perhaps adding a {{{Cache-Control: no-
 transform}}} header to the HTTP requests from cabal-install would be a
 good idea as well.

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/622#comment:1>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects