1. 21 Oct, 2021 1 commit
  2. 14 Oct, 2021 1 commit
  3. 12 Oct, 2021 1 commit
    • Andrej Shadura's avatar
      Make sure Accept-Encoding is not forwarded upstream · 3416057f
      Andrej Shadura authored
      Some HTTP clients (e.g. Go’s) like to save traffic by requesting gzip
      compression of the HTTP responses (Accept-Encoding: gzip). When the
      server supports compression, it will set Content-Encoding: gzip and
      compress the response body.
      
      However, Go’s HTTP client only transparently decoded gzip-compressed
      responses when it requests the compression on its own, but not when
      the user sets Accept-Encoding header:
      
      > DisableCompression, if true, prevents the Transport from
      > requesting compression with an "Accept-Encoding: gzip"
      > request header when the Request contains no existing
      > Accept-Encoding value. If the Transport requests gzip on
      > its own and gets a gzipped response, it's transparently
      > decoded in the Response.Body. However, if the user
      > explicitly requested gzip it is not automatically
      > uncompressed.
      
      As the result, the compressed body is returned as is, without the
      mediator knowing about it; it then spits it out to the requester without
      sett...
      3416057f
  4. 07 Oct, 2021 1 commit
  5. 06 Oct, 2021 1 commit
  6. 05 Oct, 2021 7 commits
  7. 28 Sep, 2021 1 commit
  8. 21 Sep, 2021 1 commit
  9. 31 Aug, 2021 2 commits
  10. 27 Aug, 2021 5 commits
  11. 25 Aug, 2021 3 commits
  12. 24 Aug, 2021 5 commits
  13. 11 Aug, 2021 2 commits
  14. 06 Aug, 2021 3 commits
  15. 05 Aug, 2021 1 commit
  16. 04 Aug, 2021 5 commits