From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Martin Koegler <mkoegler@auto.tuwien.ac.at>,
Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org
Subject: [PATCH] gitweb: Fix displaying unchopped argument in chop_and_escape_str
Date: Sat, 16 Feb 2008 23:07:46 +0100 [thread overview]
Message-ID: <200802162307.47323.jnareb@gmail.com> (raw)
In-Reply-To: <7vve4o7jhz.fsf@gitster.siamese.dyndns.org>
Do not use esc_html to escape [title] _attribute_ of a HTML element,
and quote unprintable characters. Replace unprintable characters by
'?' and use CGI method to generate HTML element and do the escaping.
This caused bug noticed by Martin Koegler,
Message-ID: <20080216130037.GA14571@auto.tuwien.ac.at>
that for bad commit encoding in author name, the title attribute (here
to show full, not shortened name) had embedded HTML code in it, result
of quoting unprintable characters the gitweb/HTML way. This of course
broke the HTML, causing page being not displayed in XML validating web
browsers.
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> Martin Koegler <mkoegler@auto.tuwien.ac.at> writes:
>>
>>> http://repo.or.cz/w/alt-git.git?a=shortlog
>>>
>>> fails to load in my Seamonkey browser (Debian stable):
>>>
>>> XML Parsing Error: not well-formed
>>> Location: http://repo.or.cz/w/alt-git.git?a=shortlog
>>> Line Number 561, Column 33:<td><i><span title="Uwe Kleine-K<span class="cntrl">\e</span>,Av<span class="cntrl">\e</span>(Bnig">Uwe Kleine ...</span></i></td>
>>> --------------------------------^
>>
>> It looks like gitweb uses esc_html instead of esc_param (or leaving it
>> to CGI module) title attribute of span (?) element in a shortlog.
>>
>> I'd try to fix this bug.
>
> Thanks.
And here it is. It fixes this bug; I hope there aren't any similar bugs,
but I have not checked this.
Robert Schiele wrote:
> On Sat, Feb 16, 2008 at 11:52:42AM -0800, Jakub Narebski wrote:
>>
>> It looks like gitweb uses esc_html instead of esc_param (or leaving it
>
> Huh? Isn't that the wrong escaping? esc_param is for URLs not for XML
> attributes in general, isn't it?
True, esc_param is for escaping values of CGI parameters, not for
escaping (and quoting) attributes of HTML element.
P.S. I am sorely dissapointed by the fact that CGI version 3.10 doesn't
do escaping / quoting of unprintable (control) characters in attributes
(characters outside specified character set).
gitweb/gitweb.perl | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index a89b478..acf155c 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -866,8 +866,8 @@ sub chop_and_escape_str {
if ($chopped eq $str) {
return esc_html($chopped);
} else {
- return qq{<span title="} . esc_html($str) . qq{">} .
- esc_html($chopped) . qq{</span>};
+ $str =~ s/([[:cntrl:]])/?/g;
+ return $cgi->span({-title=>$str}, esc_html($chopped));
}
}
--
1.5.4
next prev parent reply other threads:[~2008-02-16 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 13:00 Invalid html output repo.or.cz (alt-git.git) Martin Koegler
2008-02-16 19:20 ` Junio C Hamano
2008-02-16 19:52 ` Jakub Narebski
2008-02-16 20:07 ` Junio C Hamano
2008-02-16 22:07 ` Jakub Narebski [this message]
2008-02-16 21:12 ` Robert Schiele
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802162307.47323.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mkoegler@auto.tuwien.ac.at \
--cc=pasky@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).