diff options
| author | Stan Hu <stanhu@gmail.com> | 2018-08-20 15:29:41 -0700 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2018-08-23 12:40:24 -0700 |
| commit | 97cabfb65c0474742b84ec70c0d34d9f7601c59c (patch) | |
| tree | 2fb3b04b43873aba5394a2c6cb0a38e09b9cd36c /doc/gitlab-basics | |
| parent | a78c443de279b98726ed6ec5bc79df0e21dfdf41 (diff) | |
| download | gitlab-ce-97cabfb65c0474742b84ec70c0d34d9f7601c59c.tar.gz | |
Send required object storage PUT headers in /uploads/authorize API
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.
See https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/297 as well.
Diffstat (limited to 'doc/gitlab-basics')
0 files changed, 0 insertions, 0 deletions