fix handling of multiple Content-type headers
This can happen if an error happens while sending
application/mercurial-0.1 content. The error page will
be sent resulting (for at least lighttpd) in the following
headers:
Content-type: application/mercurial-0.1
Content-type: text/html
which result in req.proto = 'application/mercurial-0.1, text/html'
fix issue344
<table class="logEntry parity#parity#">
<tr>
<th class="age">#date|age# ago:</th>
<th class="firstline">#desc|strip|firstline|escape#</th>
</tr>
<tr>
<th class="revision">changeset #rev#:</th>
<td class="node"><a href="#url#rev/#node|short#{sessionvars%urlparameter}">#node|short#</a></td>
</tr>
#parent%changelogparent#
#child%changelogchild#
#changelogtag#
<tr>
<th class="author">author:</th>
<td class="author">#author|obfuscate#</td>
</tr>
<tr>
<th class="date">date:</th>
<td class="date">#date|date#</td>
</tr>
<tr>
<th class="files"><a href="#url#file/#node|short#{sessionvars%urlparameter}">files</a>:</th>
<td class="files">#files#</td>
</tr>
</table>