I'm attempting to get gitweb (git 1.8.4.2, via git instaweb) in a project dir on my Debian server to offer blame views.

In my /etc/gitweb.conf:

… # default logo, favicon, etc. settings

$feature{'blame'}{'default'} = [1];
$feature{'pickaxe'}{'default'} = [1];
$feature{'snapshot'}{'default'} = ['tgz', 'txz', 'zip'];
$feature{'highlight'}{'default'} = [1];
$feature{'pathinfo'}{'default'} = [1];

In my global config file:

[gitweb]
    blame = true
    snapshot = tgz, txz, zip
    patches = 256
    avatar = gravatar
[instaweb]
    local = false
    httpd = apache2 -f
    port = 4321

In my project's .git/config file:

[gitweb]
        blame = true

And yet, when I try to load a git blame view (via hand-modifying the URL to http://myserversip:4321/?p=.git;a=blame;f=Tests/InchCoordProxyTests.m;h=b4b2…;hb=53b4, since blame action links don't show up):

Doing a quick search for “Blame view not allowed” in the gitweb.cgi source reveals plainly that the gitweb_check_feature('blame') conditional is failing.

What am I doing wrong?

Or, is there a way to verbosely print out why gitweb is doing what it's doing (e.g. which config files were read, which settings were loaded from each file, etc.)?