Rails already sets Cache-Control according to the project visibility.
Always setting the header value to `private` prevents us from doing
proper caching (e.g. at CDN level) for public projects.

Related to https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6829

Add CI jobs for dependency scanning and static analysis

See merge request gitlab-org/gitlab-workhorse!458

Prepare 8.22.0 release

See merge request gitlab-org/gitlab-workhorse!460

Add friendly development error page for 502

See merge request gitlab-org/gitlab-workhorse!453

Bump the version of golang.org/x/sys

Closes #246

See merge request gitlab-org/gitlab-workhorse!456

Release v8.21.0

See merge request gitlab-org/gitlab-workhorse!457

Add route for group imports direct upload

See merge request gitlab-org/gitlab-workhorse!455

Sign requests that go through direct_upload

See merge request gitlab-org/security/gitlab-workhorse!1

This commit is part of a security fix, details on the issues are
available at https://gitlab.com/gitlab-org/security/gitlab/issues/21

Release v8.19.0

See merge request gitlab-org/gitlab-workhorse!452

Use multipart uploads for nuget packages

See merge request gitlab-org/gitlab-workhorse!451

Release v8.18.0

See merge request gitlab-org/gitlab-workhorse!450

Update environment websocket route

See merge request gitlab-org/gitlab-workhorse!449

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Allow inline PDF files

See merge request gitlab-org/gitlab-workhorse!446

Allow inline content disposition for PDF files

Fix typo in Gitaly RPC in CHANGELOG

See merge request gitlab-org/gitlab-workhorse!448

Renames CompleteMultiparytUpload -> CompleteMultipartUpload

Release v8.17.0

See merge request gitlab-org/gitlab-workhorse!447

Log duration_ms when Workhorse hits a bad gateway

See merge request gitlab-org/gitlab-workhorse!445

Previously when the upstream application (e.g. Unicorn) timed out,
Workhorse would report an error message of the form:

```json
{
  "correlation_id": "k4mKg0snXG3",
  "error": "badgateway: failed after 61s: EOF",
  "level": "error",
  "method": "GET",
  "msg": "error",
  "time": "2019-12-02T22:05:09-08:00",
  "uri": "/admin"
}
```

Since Sentry attempts to group similar events by some fingerprint that
includes the message, the changes in timings would trick Sentry into
creating a new event. To avoid that, the new log message now looks like:

```json
{
  "correlation_id": "k4mKg0snXG3",
  "duration_ms": 60599,
  "error": "badgateway: failed to receive response: EOF",
  "level": "error",
  "method": "GET",
  "msg": "error",
  "time": "2019-12-02T22:05:09-08:00",
  "uri": "/admin"
}
```

The inclusion of `duration_ms` and the standardized `error` message makes
it easier for users to filter and parse this error.

Add labkit monitoring for build metrics

See merge request gitlab-org/gitlab-workhorse!440

Labkit monitoring exposes a metric I wanted to add, gitlab_build_info.
This will set a gauge to the current version and build time, and as such
we can measure how fast deploys are and when the last deploy happened.

Metric exposed looks like:
`gitlab_build_info{built="20191121.084148",version="v8.15.0-5-gde6eb66"}
1`

Release v8.16.0

See merge request gitlab-org/gitlab-workhorse!444

Set a time limit on git upload-pack requests

See merge request gitlab/gitlab-workhorse!24

Upgrade Gitaly client to v1.74.0

Closes #231

See merge request gitlab-org/gitlab-workhorse!443

Add maven route test

See merge request gitlab-org/gitlab-workhorse!442

Add NuGet route for package uploads

See merge request gitlab-org/gitlab-workhorse!441