Clone and fetch exit with code 128

[Benoit van Bogaert]

After installation and using the HTTPS interface (because of internals rules, we can not use SSH), we can create a repository, clone it, add/commit files, push, pull while the repository contains a few files.

When the repository contains more files (for instance more than 160 text files, a few KB each) and when using the HTTPS url (with SSH clone/fetch work properly), the clone and fetch commands fail without any error message but exit code 128. We are using as client git version 1.8.3.1 and 1.8.2.3.

The client just says nothing (no error reported) even if we enable logs. For instance:

export GIT_TRACE_PACKET=1

export GIT_TRACE=1

export GIT_CURL_VERBOSE=1

 The server administrator can not identify the source of the problem. I suspect that we are behind a reverse proxy...

Please, note that the following workaround works because the fetch exits code 128 but leave the .git folder while clone remove the just created folder:

                git init

                git remote add origin https://www.example.com/myunit_bitbucket/myproject/myrepo/sandbox.git

                git -c http.sslVerify=false fetch origin

                git -c http.sslVerify=false pull sassc master

I am reluctant to go to production with such a doubtful solution. What do you recommend?