René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"5.6.0 https url:  [Error: HTTP parser error: unexpected content-length header]","articleBody":"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\n\n```\n[Error: HTTP parser error: unexpected content-length header]\n```\n\nstandard clone example will reproduce this error\n\n```\n nodegit.Clone(\n// basic auth bitbucket repo is what I was testing\n    \"https://user:pass@bitbucket.org/repo.git\",\n    path,\n    {\n      fetchOpts: {\n        callbacks: {\n          certificateCheck: function() {\n            // github will fail cert check on some OSX machines\n            // this overrides that check\n            return 1;\n          }\n        }\n      }\n    })\n```\n\nnode 5.5.0 works as expected\n\nthis 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\n","author":{"url":"https://github.com/pkoretic","@type":"Person","name":"pkoretic"},"datePublished":"2016-02-19T13:54:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":16},"url":"https://github.com/911/nodegit/issues/911"}