All of lore.kernel.org
 help / color / mirror / Atom feed
From: sf <sf@b-i-t.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Oleg Verych <olecom@flower.upol.cz>,
	Junio C Hamano <junkio@cox.net>,
	Li Yang-r58472 <LeoLi@freescale.com>,
	rea-git@codelabs.ru, Raimund Bauer <ray@softwarelandschaft.com>,
	git@vger.kernel.org, Alp Toker <alp@atoker.com>
Subject: Re: (Re: gitweb not friendly to firefox?) and unusable in the lynx
Date: Thu, 08 Mar 2007 16:31:50 +0100	[thread overview]
Message-ID: <45F02C66.9010909@b-i-t.de> (raw)
In-Reply-To: <200703030357.18822.jnareb@gmail.com>

Jakub Narebski wrote:
...
> By "conservatively" it means that it uses 'application/xhtml+xml' only when
> client explicitly claims that it accepts its, and it is not due to for
> example */* accept globbing.

You may need something like the (not tested and line wrapped) patch 
below as well.

Regards

Stephan


diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index 27b5970..6cc5c20 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -1714,7 +1714,8 @@ sub git_header_html {
                 $content_type = 'text/html';
         }
         print $cgi->header(-type=>$content_type, -charset => 'utf-8',
-                          -status=> $status, -expires => $expires);
+                          -status=> $status, -expires => $expires,
+                          -Vary=> 'Accept');
         my $mod_perl_version = $ENV{'MOD_PERL'} ? " $ENV{'MOD_PERL'}" : '';
         print <<EOF;
  <?xml version="1.0" encoding="utf-8"?>

      parent reply	other threads:[~2007-03-08 15:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 10:57 gitweb not friendly to firefox? Li Yang-r58472
2007-03-01 11:34 ` Andy Parkins
2007-03-01 11:54   ` Li Yang-r58472
2007-03-01 11:56   ` Junio C Hamano
2007-03-01 13:34 ` Raimund Bauer
2007-03-01 14:00   ` Eygene Ryabinkin
2007-03-01 14:26     ` Raimund Bauer
2007-03-02  2:28     ` Li Yang-r58472
2007-03-02  4:40       ` Junio C Hamano
2007-03-02  6:47         ` Li Yang-r58472
2007-03-02  6:51           ` Junio C Hamano
2007-03-02  9:36             ` Li Yang-r58472
2007-03-02 10:17               ` Junio C Hamano
2007-03-02 10:27                 ` Li Yang-r58472
2007-03-02 16:19                 ` (Re: gitweb not friendly to firefox?) and unusable in the lynx Oleg Verych
2007-03-03  2:57                   ` Jakub Narebski
2007-03-03  3:25                     ` Nicolas Pitre
2007-03-03  3:41                       ` Jakub Narebski
2007-03-03  3:49                         ` Nicolas Pitre
2007-03-03  3:58                           ` Jakub Narebski
2007-03-03  4:34                             ` Nicolas Pitre
2007-03-04  0:49                               ` Jakub Narebski
2007-03-04  9:47                                 ` Uwe Kleine-König
2007-03-03  5:09                           ` Nicolas Pitre
2007-03-03 13:04                             ` Oleg Verych
2007-03-03 13:25                             ` Johannes Schindelin
2007-03-03 13:29                       ` Junio C Hamano
2007-03-03 14:19                         ` Oleg Verych
2007-03-08 15:31                     ` sf [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=45F02C66.9010909@b-i-t.de \
    --to=sf@b-i-t.de \
    --cc=LeoLi@freescale.com \
    --cc=alp@atoker.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=junkio@cox.net \
    --cc=olecom@flower.upol.cz \
    --cc=ray@softwarelandschaft.com \
    --cc=rea-git@codelabs.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.