With node 5.6.0 which fixes https parsing errors and changes current parsing behavior (https://nodejs.org/en/blog/vulnerability/february-2016-security-releases) trying to git clone or rebase https bitbucket private url results in
[Error: HTTP parser error: unexpected content-length header]
standard clone example will reproduce this error
nodegit.Clone(
// basic auth bitbucket repo is what I was testing
"https://user:pass@bitbucket.org/repo.git",
path,
{
fetchOpts: {
callbacks: {
certificateCheck: function() {
// github will fail cert check on some OSX machines
// this overrides that check
return 1;
}
}
}
})
node 5.5.0 works as expected
this seems like an error from http-parser itself so I don't know if this is really related to nodegit, since I'm very short on time to do some more debugging
Reactions are currently unavailable
With node 5.6.0 which fixes https parsing errors and changes current parsing behavior (https://nodejs.org/en/blog/vulnerability/february-2016-security-releases) trying to git clone or rebase https bitbucket private url results in
standard clone example will reproduce this error
nodegit.Clone( // basic auth bitbucket repo is what I was testing "https://user:pass@bitbucket.org/repo.git", path, { fetchOpts: { callbacks: { certificateCheck: function() { // github will fail cert check on some OSX machines // this overrides that check return 1; } } } })node 5.5.0 works as expected
this seems like an error from http-parser itself so I don't know if this is really related to nodegit, since I'm very short on time to do some more debugging