Re: Bug report: Git 1.8 on Ubuntu 13.10 refs not valid

[Jeff King <peff@peff.net>]

On Mon, Mar 31, 2014 at 07:19:09PM +0200, Siggi wrote:

> here are the two outputs you wanted to see.

The interesting bit is at the end...

> < HTTP/1.1 200 OK
> < Date: Mon, 31 Mar 2014 17:04:57 GMT
> * Server Apache/2.2.22 (Ubuntu) is not blacklisted
> < Server: Apache/2.2.22 (Ubuntu)
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.19
> < ETag: "2ab570112563de50022189f0a2ffcdd4"
> < Pragma: no-cache
> < Expires: Fri, 01 Jan 1980 00:00:00 GMT
> < X-Runtime: 72
> < Cache-Control: no-cache, max-age=0, must-revalidate
> < Content-Length: 1047
> < Status: 200
> < Content-Type: application/x-git-upload-pack-advertisement; charset=utf-8

This content-type is the problem. There should not be a charset
parameter (it is meaningless, and it throws off git's content-type
check). So your web server configuration (or the redmine git plugin)
should be fixed, but you'll have to talk to redmine folks to figure that
part out.

That being said, git _could_ be more liberal in accepting a content-type
with parameters (even though it does not know about any parameters, and
charset here is completely meaningless). I have mixed feelings on that.

-Peff