From: "J.H." <warthog19@eaglescrag.net>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: bug with gitweb on kernel.org
Date: Tue, 24 Apr 2007 01:19:48 -0700 [thread overview]
Message-ID: <1177402788.5357.30.camel@localhost.localdomain> (raw)
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:
> 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
prev parent reply other threads:[~2007-04-24 8:27 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
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. [this message]
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=1177402788.5357.30.camel@localhost.localdomain \
--to=warthog19@eaglescrag.net \
--cc=git@vger.kernel.org \
--cc=nico@cam.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).