Gitlab fails to work with gzip content-encoding on openwrt git-client
I run my own gitlab server, version 12.4.1ce. Since I updated to this version, the git client on openwrt 18.0.6 fails. On a git clone (command line git version 2.16.3) I get: "Unrecognized content encoding type. libcurl understands identity content encodings". After a lot of research, I found:
- If I force the server to NOT gzip the content (although the git client has Accept-Enconding: gzip), it works again. I forced this by adding a proxy_set_header Accept-Encoding "identity"; to /var/opt/gitlab/nginx/conf/gitlab-http.conf. Of course this setting will be lost after a gitlab-ctl reconfigure.
- If I try any gitHUB server, it works ok WITH gzip. Also from openwrt. So it seems that the openwrt git client tries to unzip the server response, fails, and then gives this error about missing content encodings.
- If I try the standard gitlab.com server, I have the same problem. So it is not just a problem with our instance.
- tested with curl -s -H "Accept-Encoding: gzip" url > out.gz: for gitlab AND github the resulting file successfully unzips with gzip -d out.gz. So at least unzipping by hand works. So the payload is correctly zipped. Where does it go wrong in the git-client?