Re: bug with gitweb on kernel.org
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Apr 24, 2007, 01:06 UTC
- Message-ID
- <f0jkvm$31p$1@sea.gmane.org>
- In-Reply-To
- <1177294925.24896.48.camel@localhost.localdomain>
J.H. wrote:
Show 6 quoted lines
> 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