git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Simons <simons@cryp.to>
To: git@vger.kernel.org
Subject: gitweb sets incorrect <base> header
Date: Tue, 28 Apr 2009 14:41:11 +0200	[thread overview]
Message-ID: <877i15uf14.fsf@write-only.cryp.to> (raw)

Hi,

after a recent gitweb update to revision v1.6.3-rc3-12-gb79376c, the CGI now
generates an incorrect <base> header. For example, the first "patch" on the
page

  http://git.cryp.to/fastcgi/commitdiff/9ad9965b3fa293c458df14391f181f2f8f1197cd

erroneously refer to http://git.cryp.to/cgi-bin/gitweb.cgi#patch1, but that
page doesn't exist. It appears that $base_url is not determined correctly.

Does anyone have a clue how that problem can be fixed?

Take care,
Peter

             reply	other threads:[~2009-04-28 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 12:41 Peter Simons [this message]
2009-04-29  9:22 ` gitweb sets incorrect <base> header Giuseppe Bilotta
2009-04-29  9:33 ` Jakub Narebski
2009-04-30 10:06   ` Peter Simons

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=877i15uf14.fsf@write-only.cryp.to \
    --to=simons@cryp.to \
    --cc=git@vger.kernel.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).