1. 17 Mar, 2016 3 commits
  2. 16 Mar, 2016 7 commits
  3. 14 Mar, 2016 1 commit
  4. 13 Mar, 2016 5 commits
  5. 12 Mar, 2016 4 commits
  6. 11 Mar, 2016 5 commits
  7. 10 Mar, 2016 2 commits
  8. 08 Mar, 2016 1 commit
  9. 07 Mar, 2016 3 commits
  10. 06 Mar, 2016 2 commits
  11. 03 Mar, 2016 2 commits
  12. 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
  13. 01 Mar, 2016 1 commit
  14. 27 Feb, 2016 2 commits