1. 09 Jun, 2016 1 commit
  2. 07 Jun, 2016 1 commit
  3. 06 Jun, 2016 2 commits
  4. 03 Jun, 2016 1 commit
    • Brandon Black's avatar
      Correctly handle HTTP/1.1 EOF response · f07287a6
      Brandon Black authored
      Commit e142a199 for Issue #1918 fixed up the case where the
      server sends an HTTP/1.1 response with no Content-Length, no
      Transfer-Encoding, but with Connection:close.
      
      This fixes the very similar case where all the conditions are the
      same except that there's also no Connection: close header, but the
      content is still implicitly delimited by the server closing the
      connection.
      
      This behavior has been observed from multiple versions of Apache
      with WSGI applications behind it, resulting in broken
      Content-Length:0 responses from Varnish.
      
      Ref: varnishcache/varnish-cache#1954
      f07287a6
  5. 01 Jun, 2016 4 commits
  6. 31 May, 2016 7 commits
  7. 30 May, 2016 3 commits
  8. 25 May, 2016 10 commits
  9. 19 May, 2016 1 commit
  10. 11 May, 2016 1 commit
  11. 03 May, 2016 1 commit
  12. 02 May, 2016 2 commits
  13. 29 Apr, 2016 1 commit
  14. 28 Apr, 2016 1 commit
  15. 26 Apr, 2016 1 commit
  16. 25 Apr, 2016 3 commits
    • Pål Hermunn Johansen's avatar
      Backend mode in varnishncsa · 5a46b8c9
      Pål Hermunn Johansen authored
      A new mode, backend mode, in varnishncsa is introduced. It lets you
      log trafic from varnish to the backends. The normal (default) mode is
      now named "client mode" and can be explicitly selected using -c. You
      can run varnishncsa in backend mode in addition to varnishncsa in
      client mode, but it is also possible to run in mixed mode by
      specifying both -b and -c.
      
      New formatter added: %{Varnish:side}x will be either "b" or "c",
      depending on where the request was made.
      5a46b8c9
    • Martin Blix Grydeland's avatar
      Add a SLT_BackendStart log tag, and log address and port on backend req · 3b078764
      Martin Blix Grydeland authored
      This log record is a counterpart to the SLT_ReqStart for backends, and
      shows the socket endpoint we are talking to at the start of backend
      requests. Today this information is only logged on opening a backend
      connection (SLT_BackendOpen), and is thus not available on the backend
      log transaction when on a reused backend connection.
      
      We need this information to complete the backend view varnishncsa
      extension.
      3b078764
    • Pål Hermunn Johansen's avatar
      Add simple error checking in ESI processing · ea11249a
      Pål Hermunn Johansen authored
      When the VEP state machine is in a bad state during finalization
      (VEP_Finish), we log this as an ESI error.
      ea11249a