This is based on Kamil's work in
https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/5 .

Replace "auth request" with middleware

This gives us the flexibility we need to also handle regular downloads
and uploads in gitlab-workhorse.

See merge request !6

This gives us the flexibility we need to also handle regular
downloads and uploads in gitlab-workhorse.

Accomodate broken HTTP clients

HTTP header lookups are supposed to be case-insensitive but some
clients do a case insensitive lookup, which breaks because of Go's
header canonicalization.

See merge request !2

Pass LD_LIBRARY_PATH to the git command

As gitlab-shell does in https://gitlab.com/gitlab-org/gitlab-shell/blob/master/lib/gitlab_shell.rb#L126

LD_LIBRARY_PATH is needed when using Software Collections for instance but there are probably many other scenarios that need it as well. It was passed to git (and from git to hooks) by gitlab-shell, and still is for SSH access, but it was not the case anymore for HTTP access with the introduction of gitlab-git-http-server/git-workhorse.


See merge request !1

"git archive" download support

This needs changes in GitLab and gitlab_git too.

See merge request !2

I solved the problem in cookbook-gitlab-test

Use our own header instead of User-Agent

This will still help routing in HTTP proxies, while also allowing
gitlab-rails to see the User-Agent.

See merge request !6

Forward Host header to the auth backend

The Host header is handled specially by the Go http library and
needs special processing in order to have it forwarded with the
other headers to the auth backend.

This allows the Host header received by the backend to be consistent with other 
requests not going through gitlab-git-http-server.


See merge request !5

The Host header is handled specially by the Go http library and
needs special processing in order to have it forwarded with the
other headers to the auth backend.