1. 29 Oct, 2018 2 commits
    • Ben Kochie's avatar
      Update redigo library · 6473b6e4
      Ben Kochie authored
      Use updated upstream vendor for redigo/sentinel libraries.
      6473b6e4
    • Ben Kochie's avatar
      General vendoring cleanup · 11d5df02
      Ben Kochie authored
      * Fetch all vendors to make sure vendor.json has all the correct fields.
      * Select master or version tag where appropriate.
      * Bring many vendorings up to date with current code.
      11d5df02
  2. 26 Oct, 2018 2 commits
  3. 23 Oct, 2018 3 commits
  4. 22 Oct, 2018 1 commit
  5. 19 Oct, 2018 2 commits
  6. 18 Oct, 2018 2 commits
  7. 04 Oct, 2018 3 commits
  8. 28 Sep, 2018 3 commits
  9. 27 Sep, 2018 1 commit
  10. 26 Sep, 2018 3 commits
  11. 24 Sep, 2018 1 commit
  12. 20 Sep, 2018 1 commit
  13. 05 Sep, 2018 1 commit
  14. 04 Sep, 2018 3 commits
    • Stan Hu's avatar
      Release GitLab Workhorse v6.1.0 · dde84d84
      Stan Hu authored
      dde84d84
    • Nick Thomas's avatar
      Merge branch 'sh-object-storage-put-headers' into 'master' · 23b09948
      Nick Thomas authored
      Support adding PUT headers for object storage from Rails
      
      See merge request gitlab-org/gitlab-workhorse!297
      23b09948
    • Stan Hu's avatar
      Support adding PUT headers for object storage from Rails · 7231f85e
      Stan Hu authored
      As revealed in https://gitlab.com/gitlab-org/gitlab-ce/issues/49957, Rails
      generates a signed URL with a fixed HTTP header with `Content-Type:
      application/octet-stream`. However, if we change or remove that for
      some reason in Workhorse, this breaks the upload with a 403 Unauthorized because
      the signed URL is not valid.
      
      We can make this more robust by doing the following:
      
      1. In the `/uploads/authorize` request, Rails can return a `StoreHeaders` key-value
      pair in the JSON response containing the required headers that the PUT
      request must include.
      2. Use those HTTP headers if that value is present.
      3. For backwards compatibility, if that key is not present, default to
      the old behavior of sending the fixed `Content-Type` header.
      7231f85e
  15. 29 Aug, 2018 1 commit
  16. 23 Aug, 2018 3 commits
  17. 17 Aug, 2018 3 commits
  18. 15 Aug, 2018 2 commits
  19. 14 Aug, 2018 2 commits
  20. 07 Aug, 2018 1 commit