1. 13 Mar, 2016 4 commits
  2. 12 Mar, 2016 3 commits
  3. 11 Mar, 2016 5 commits
  4. 07 Mar, 2016 3 commits
  5. 06 Mar, 2016 2 commits
  6. 03 Mar, 2016 2 commits
  7. 02 Mar, 2016 2 commits
    • Matthew Holt's avatar
    • Matthew Holt's avatar
      Revert recent Content-Length-related changes and fix fastcgi return · 2a46f2a1
      Matthew Holt authored
      fastcgi's ServeHTTP method originally returned the correct value (0) in
      b51e8bc1. Later, I mistakenly suggested
      we change that to return the status code because I forgot that status
      codes aren't logged by the return value. So fastcgi broke due in
      3966936b due to my error.
      
      We later had to try to make up for this with ugly Content-Length checks
      like in c37ad7f6. Turns out that all we
      had to do was fix the returned status here back to 0. The proxy
      middleware behaves the same way, and returning 0 is correct. We should
      only return a status code if the response has not been written, but with
      upstream servers, we do write a response; they do not know about our
      error handler.
      
      Also clarifed this in the middleware.Handler documentation.
      2a46f2a1
  8. 01 Mar, 2016 1 commit
  9. 27 Feb, 2016 2 commits
  10. 26 Feb, 2016 1 commit
    • Matthew Holt's avatar
      Implant version information with -ldflags with help of build script · da08c94a
      Matthew Holt authored
      Without -ldflags, the verison information needs to be updated manually,
      which is never done between releases, so development builds appear
      indiscernable from stable builds using `caddy -version`.
      
      This is part of a set of changes intended to relieve the burden of
      always updating version information manually and distributing binaries
      that look stable but actually may not be.
      
      A stable build is defined as one which is produced at a git tag with
      a clean working directory (no uncommitted changes). A dev build is
      anything else. With this build script, `caddy -version` will now reveal
      whether it is a development build and, if so, the base version, the
      latest commit, the date and time of build, and the names of files with
      changes as well as how many changes were made.
      
      The output of `caddy -version` for stable builds remains the same.
      da08c94a
  11. 25 Feb, 2016 3 commits
  12. 24 Feb, 2016 7 commits
  13. 23 Feb, 2016 2 commits
  14. 22 Feb, 2016 2 commits
  15. 20 Feb, 2016 1 commit