On Tue, 9 Apr 2013 05:57:47 -0700 (PDT) Oj W <ojwli...@gmail.com> wrote:
> Change a binary file whose filename contains an ampersand, then view > the commitdiff page in gitweb. > > Firefox refuses to display the commitdiff page because "XML Parsing > Error: not well-formed". (Other pages like "commit" and "tree" work > fine when showing the same file) > > Is this a known bug? A webserver configuration thing? > > Webserver here is NGINX. First 5 lines of each gitweb page are like: > > <?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC > "-//W3C//DTD XHTML 1.0 Strict//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";><html > xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en-US" > lang="en-US"><!-- git web interface version 1.7.9.5, (C) 2005-2006, > Kay Sievers <kay.siev...@vrfy.org>, Christian Gierke --><!-- git core > binaries version 1.7.9.5 --> I would just try to dump the TCP traffic of the client/server exchange while requesting that commitdiff page and see what the server sends to the client. Wireshark could be used for this (or tcpdump, with the capture file it generated inspected in Wireshark afterwards). This will allow you to either prove or disprove the assertion the generated page contains an unescaped ampersand. Also try to see if any commit in the recent gitweb commit history applies to your case [2]. In either case please direct bug reports to the main Git list (for developers) which is git at vger.kernel.org (see [1] for more info). 1. http://vger.kernel.org/vger-lists.html#git 2. https://github.com/git/git/commits/master/gitweb -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
