git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: bug with gitweb on kernel.org

From
JJ.H. <warthog19@eaglescrag.net>
Date
Apr 24, 2007, 08:19 UTC
Message-ID
<1177402788.5357.30.camel@localhost.localdomain>
In-Reply-To
<alpine.LFD.0.98.0704222112040.28339@xanadu.home>

Ok the change is out and in the wild it will likely take about 24hrs to work itself through everything. I'll check on it tomorrow to see how things are going.

- John 'Warthog9' Hawley
On Sun, 2007-04-22 at 21:16 -0400, Nicolas Pitre wrote:
Show 49 quoted lines
> On Sun, 22 Apr 2007, J.H. wrote:
> 
> > On Thu, 2007-04-19 at 23:02 -0400, Nicolas Pitre wrote:
> > > Almost 2 months ago we discussed about gitweb not properly detecting the 
> > > client's ability to deal with application/xhtml+xml, something to do 
> > > with the caching of a previous request from a client which did support 
> > > it and serving the same content to a subsequent client which does not.
> > 
> > I apparently missed that entire conversation, my apologies.
> > 
> > > 
> > > Right now www.kernel.org/git is unusable for me with lynx as it keeps 
> > > prompting:
> > > 
> > > 	application/xhtml+xml  D)ownload, or C)ancel
> > > 
> > > Is there any plan to have that fixed?
> > > 
> > 
> > Well there are a couple of quick thoughts, so far (in my quick testing)
> > lynx and IE are the only two browsers that have issues with this
> > particular bit of code.  Links, konqueror, safari, firefox, mozilla, etc
> > all seem to handle the pages without issue.
> 
> No.  You also missed that links, elinks, and the emacs one (w3m or the 
> like) were also reported to fail.  And sometimes lynx even works.
> 
> >  Taking a quick glance at the code it seems IE claims to be xhtml+xml 
> > compliant but apparently isn't really (any real surprise?) and lynx 
> > just doesn't seem to support that mime type.
> 
> Lynx and many others.  It is just a question of luch whether the served 
> page is acceptable or not.
> 
> > The simplest fix would be to eliminate the distinction between
> > applicatoin/xhtml+xml and application/html in the gitweb code (or at
> > least in the caching gitweb code) and have everything claim a mimetype
> > of application/html and let the browser sort out if it's using xhtml or
> > html from the doctype.  This would solve both the problem your seeing on
> > lynx and would make the caching gitweb usable by more IE users.
> 
> Great.
> 
> 
> Nicolas
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous: Johan HerlandNext: J.H.
Message 12 of 13 in “bug with gitweb on kernel.org”
  1. Nicolas PitreApr 20, 2007
  2. J.H.Apr 23, 2007
  3. Nicolas PitreApr 23, 2007
  4. J.H.Apr 23, 2007
  5. H. Peter AnvinApr 24, 2007
  6. H. Peter AnvinApr 24, 2007
  7. Johan HerlandApr 24, 2007
  8. Jakub NarebskiApr 24, 2007
  9. J.H.Apr 24, 2007
  10. Johan HerlandApr 24, 2007
  11. Johan HerlandApr 24, 2007
  12. J.H.Apr 24, 2007
  13. J.H.Apr 24, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.