1. 07 Nov, 2018 2 commits
  2. 06 Nov, 2018 2 commits
  3. 05 Nov, 2018 3 commits
  4. 01 Nov, 2018 1 commit
  5. 30 Oct, 2018 1 commit
  6. 29 Oct, 2018 4 commits
  7. 26 Oct, 2018 2 commits
  8. 23 Oct, 2018 3 commits
  9. 22 Oct, 2018 1 commit
  10. 19 Oct, 2018 2 commits
  11. 18 Oct, 2018 2 commits
  12. 04 Oct, 2018 3 commits
  13. 28 Sep, 2018 3 commits
  14. 27 Sep, 2018 1 commit
  15. 26 Sep, 2018 3 commits
  16. 24 Sep, 2018 1 commit
  17. 20 Sep, 2018 1 commit
  18. 05 Sep, 2018 1 commit
  19. 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
  20. 29 Aug, 2018 1 commit