Re: bug with gitweb on kernel.org

["J.H." <warthog19@eaglescrag.net>]

On Tue, 2007-04-24 at 03:06 +0200, Jakub Narebski wrote:
> 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).
> 

It's either that or store only the data not the headers and deal with
the headers on each request - but that might have other unintended
consequences I haven't thought of yet.  Anyway I think your right -
short term solution if nothing else is serve out text/html and look more
closely at the problem when I rebase.

- John 'Warthog9' Hawley