v1.4.8

Fixed

• The replay download sent Transfer-Encoding: chunked to every client,
  including ones answered with an HTTP/1.0 status line - and HTTP/1.0 has
  no chunked encoding. Browsers tolerate the contradiction; a strict
  reverse proxy does not, and reads the hex chunk lengths as part of the
  recording. The framing now follows the version the client actually
  spoke: HTTP/1.1 gets a 1.1 status line and chunked (its terminator is
  how a client knows the download finished rather than died), HTTP/1.0
  gets the body bare, delimited by the connection close. Reported by a
  deployment sitting behind such a proxy.