1. 06 Nov, 2018 1 commit
  2. 05 Nov, 2018 1 commit
    • Kenton Varda's avatar
      Allow WebSocket to keep sending after close(). · 308e5cda
      Kenton Varda authored
      In Cloudflare Workers, we've observed applications in the wild that continue to send messages after a Close message. This is incorrect, but it happens, and we end up logging a spurious error as we attempt to proxy the message through.
      
      By removing this restriction, we can now proxy these WebSockets despite the incorrect usage.
      308e5cda
  3. 29 Oct, 2018 2 commits
  4. 26 Oct, 2018 1 commit
  5. 20 Oct, 2018 1 commit
  6. 12 Oct, 2018 2 commits
    • Kenton Varda's avatar
      Merge pull request #751 from… · f73ac9f6
      Kenton Varda authored
      Merge pull request #751 from capnproto/harris/zero-length-responses-get-no-content-length-and-great-sadness
      
      Zero-length HTTP responses get no Content-Length header
      f73ac9f6
    • Harris Hancock's avatar
      Zero-length HTTP responses to HEAD get no Content-Length header · 48083d47
      Harris Hancock authored
      There is currently no way to explicitly omit a Content-Length/Transfer-Encoding header on an HTTP response to a HEAD request. This is awkward for a proxy, which would ideally pass along responses as-is, even if they have no such headers.
      
      This change allows an author to pass zero as the expected body length to HttpService::Response::send() to mean "do not set any body header." This means that a proxy might strip Content-Length: 0 headers, but will never add a Content-Length header where there was none before.
      48083d47
  7. 10 Oct, 2018 2 commits
  8. 08 Oct, 2018 1 commit
  9. 07 Oct, 2018 3 commits
  10. 27 Sep, 2018 4 commits
  11. 25 Sep, 2018 2 commits
  12. 17 Sep, 2018 1 commit
  13. 16 Sep, 2018 3 commits
  14. 11 Sep, 2018 1 commit
  15. 10 Sep, 2018 1 commit
  16. 08 Sep, 2018 2 commits
  17. 07 Sep, 2018 1 commit
    • Oleg Kolosov's avatar
      Change KJ_LOG macro to use "for" statement · 11ee5380
      Oleg Kolosov authored
      Using "for" statement instead of "if", as suggested by Kenton, still
      avoids "dangling else" warnings and also allows to have diagnostics on
      missing ";" at the end. So this way is better.
      11ee5380
  18. 05 Sep, 2018 1 commit
  19. 02 Sep, 2018 1 commit
  20. 31 Aug, 2018 1 commit
  21. 30 Aug, 2018 1 commit
  22. 29 Aug, 2018 3 commits
  23. 26 Aug, 2018 4 commits