Skip to content

Set BasicAuth in http.go only if username and password are not empty #914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 13, 2022
Merged

Set BasicAuth in http.go only if username and password are not empty #914

merged 1 commit into from
Jul 13, 2022

Conversation

clns
Copy link
Contributor

@clns clns commented Apr 21, 2022

This prevents error "read/write on closed pipe".

Go's http.client::send() always closes req.Body, so if the first request attempt
is unsuccessful, any subsequent requests after calling the CredentialsCallback
will attempt to read/write on a closed pipe.
@clns
Set BasicAuth in http.go only if username and password are not empty
8f82899 
This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe.
@lhchavez lhchavez merged commit 9db5de1 into libgit2:main Jul 13, 2022
github-actions bot pushed a commit that referenced this pull request Jul 13, 2022
@clns @lhchavez
Set BasicAuth in http.go only if username and password are not empty (#…
38313ce 
…914) This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe. (cherry picked from commit 9db5de1)
github-actions bot pushed a commit that referenced this pull request Jul 13, 2022
@clns @lhchavez
Set BasicAuth in http.go only if username and password are not empty (#…
ea4c1f0 
…914) This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe. (cherry picked from commit 9db5de1)
github-actions bot pushed a commit that referenced this pull request Jul 13, 2022
@clns @lhchavez
Set BasicAuth in http.go only if username and password are not empty (#…
ea645bc 
…914) This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe. (cherry picked from commit 9db5de1)
github-actions bot pushed a commit that referenced this pull request Jul 13, 2022
@clns @lhchavez
Set BasicAuth in http.go only if username and password are not empty (#…
c23efac 
…914) This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe. (cherry picked from commit 9db5de1)
github-actions bot pushed a commit that referenced this pull request Jul 13, 2022
@clns @lhchavez
Set BasicAuth in http.go only if username and password are not empty (#…
a4105aa 
…914) This prevents error "read/write on closed pipe". Go's http.client::send() always closes req.Body, so if the first request attempt is unsuccessful, any subsequent requests after calling the `CredentialsCallback` will attempt to read/write on a closed pipe. (cherry picked from commit 9db5de1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants

@clns @lhchavez