1. 30 Nov, 2019 1 commit
  2. 29 Nov, 2019 1 commit
  3. 27 Nov, 2019 4 commits
  4. 22 Nov, 2019 4 commits
  5. 19 Nov, 2019 2 commits
  6. 17 Nov, 2019 6 commits
  7. 07 Nov, 2019 1 commit
  8. 05 Nov, 2019 1 commit
  9. 13 Oct, 2019 5 commits
  10. 12 Oct, 2019 2 commits
    • Tiago's avatar
      using byteslice instead of slice for buffer manipulation · 933d319b
      Tiago authored
      The code from which the buffer and string handling was adapted,
      inherited also the usage of slice!, which is not the appropriate tool
      for when dealing with byte streams. Ruby doesn't have an equivalent
      String#byteslice! yet, so we adapted other known workarounds (see
      https://bugs.ruby-lang.org/issues/13626) for our code. This means that:
      
      - For HTTPX::Buffer, we add a shift! method, as all usage shift the
      buffer part which has been written to the socket;
      - For HTTP1 parser and Chunker, we have to double the usage of
      byteslice. In the cases where it results in nil, we might needlessly
      initialize an empty string, however this is the lesser of evils, until a
      proper backport is in place.
      933d319b
    • Tiago's avatar
      compression: added some behaviours from net-http · a059726b
      Tiago authored
      After looking at net-http code, decided to adopt the following
      behaviour:
      
      * do not send accept-encoding when sending Range header
      * remove content-encoding from response headers as we decode them
      
      in order for user code to track what was decoded, added
      HTTPX::Response::Body#encodings, which returns the array of encodings
      for which the body was successfully decoded
      a059726b
  11. 11 Oct, 2019 1 commit
  12. 08 Oct, 2019 1 commit
  13. 07 Oct, 2019 4 commits
  14. 29 Sep, 2019 3 commits
  15. 28 Sep, 2019 1 commit
  16. 27 Sep, 2019 3 commits