summaryrefslogtreecommitdiff
path: root/client/httpclient.go
Commit message (Collapse)AuthorAgeFilesLines
* Deprecate self_signed_cert config settingid-deprecate-self-signed-certIgor Drozdov2022-01-121-1/+4
| | | | | | | | | The option isn't required to accept self-signed certs On the other hand, if the option set to true it makes machine-in-the-middle attack possible Let's clarify it in the code that the option is deprecated
* Merge branch 'fix/name-certificate' into 'main'Igor Drozdov2021-10-121-1/+0
|\ | | | | | | | | refactor: remove call to BuildNameToCertificate (deprecated) See merge request gitlab-org/gitlab-shell!515
| * refactor: remove call to BuildNameToCertificate (deprecated)feistel2021-09-081-1/+0
| |
* | Only validate SSL cert file exists if a value is suppliedStan Hu2021-09-231-4/+18
|/ | | | | | | | | This fixes a regression in https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/508. If an HTTPS internal API URL were used, gitlab-shell would not work at all. We now handle blank `caFile` properly. Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/529
* refactor: move away from ioutil (deprecated)feistel2021-08-191-3/+2
|
* test: move os.stat check before the hcc creationAsh McKenzie2021-08-171-7/+7
|
* fix: make sure ErrCafileNotFound is returned only when the file doesn't existfeistel2021-08-111-1/+4
|
* fix: validate client cert paths exist on disk before proceedingfeistel2021-08-111-9/+19
|
* Fix formatting via make fmtStan Hu2021-07-261-1/+1
|
* Switch to labkit/log for logging functionalityIgor Drozdov2021-07-221-1/+1
|
* Add tracing instrumentation to http clientIgor2021-07-201-1/+2
|
* Update httpclient.go with TLS 1.2 as minimum versionVitor Meireles De Sousa2020-11-171-0/+1
|
* GitLab API Client support for client certificatesPaul Okstad2020-11-171-14/+67
|
* Fix gitlab-shell not handling relative URLs over UNIX socketssh-fix-unix-relative-url-accessStan Hu2020-08-201-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4498#note_397401883, if you specify a relative path such as: ``` external_url 'http://gitlab.example.com/gitlab' ``` gitlab-shell doesn't have a way to pass the `/gitlab` to the host. For example, let's say we have: ``` gitlab_url: "http+unix://%2Fvar%2Fopt%2Fgitlab%2Fgitlab-workhorse%2Fsocket" ``` If we have `/gitlab` as the relative path, how do we specify what is the UNIX socket path and what is the relative path? If we specify: ``` gitlab_url: "http+unix:///var/opt/gitlab/gitlab-workhorse.socket/gitlab ``` This is ambiguous. Is the socket in `/var/opt/gitlab/gitlab-workhorse.socket/gitlab` or in `/var/opt/gitlab/gitlab-workhorse.socket`? To fix this, this merge request adds an optional `gitlab_relative_url_root` config parameter: ``` gitlab_url: "http+unix://%2Fvar%2Fopt%2Fgitlab%2Fgitlab-workhorse%2Fsocket" gitlab_relative_url_root: /gitlab ``` This is only used with UNIX domain sockets to disambiguate the socket and base URL path. If `gitlab_url` uses `http://` or `https://`, then `gitlab_relative_url_root` is ignored. Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/476
* Generate and log correlation IDsStan Hu2020-07-311-1/+4
| | | | | This will make it easier to tie an SSH access request to Rails API and Gitaly requests.
* Move gitlabnet client to client packagejc-refactor-gitlabnet-clientJohn Cai2020-05-041-0/+113
View Lorry Controller Status