From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: bug with gitweb on kernel.org
Date: Tue, 24 Apr 2007 03:06:51 +0200 [thread overview]
Message-ID: <f0jkvm$31p$1@sea.gmane.org> (raw)
In-Reply-To: 1177294925.24896.48.camel@localhost.localdomain
J.H. wrote:
> Well the only difference in the pages being served is the mime type
> application/html vs. application/xhtml+xml. Does anyone know the
> original impetus to using application/xhtml+xml (despite the fact that
> it's technically the correct choice) vs. just using application/html for
> everything? I'm sure there was a good reason behind it and I'd rather
> know what that reason was before I got changing things
The idea was to serve application/xhtml+xml to browsers which _explicitely_
support it. But coupled with the fact that gitweb on kernel.org is modified
gitweb with caching, and it looks like it caches also HTTP headers...
I think simplest solution would be to remove complication, and always serve
text/html (at least for kernel.org gitweb with caching modifications).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-04-24 1:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 3:02 bug with gitweb on kernel.org Nicolas Pitre
2007-04-23 0:09 ` J.H.
2007-04-23 1:16 ` Nicolas Pitre
2007-04-23 2:22 ` J.H.
2007-04-24 0:18 ` H. Peter Anvin
2007-04-24 0:44 ` H. Peter Anvin
2007-04-24 6:40 ` Johan Herland
2007-04-24 1:06 ` Jakub Narebski [this message]
2007-04-24 1:06 ` J.H.
2007-04-24 7:40 ` Johan Herland
[not found] ` <200704240933.58680.johherla@online.no>
2007-04-24 7:50 ` J.H.
2007-04-24 6:42 ` Johan Herland
2007-04-24 8:19 ` J.H.
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='f0jkvm$31p$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).