From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Tadeusz Sosnierz <tadzikes@gmail.com>, Eric Wong <normalperson@yhbt.net>
Subject: [BUGFIX PATCH 1/4] git-instaweb: Fix issue with static files for 'plackup' server
Date: Wed, 29 Dec 2010 17:47:00 +0100 [thread overview]
Message-ID: <201012291747.01288.jnareb@gmail.com> (raw)
In-Reply-To: <201012291743.41213.jnareb@gmail.com>
The default (in gitweb/Makefile) is to use relative paths for gitweb
static files, e.g. "static/gitweb.css" for GITWEB_CSS. But the
configuration for Plack::Middleware::Static in plackup_conf assumed
that static files must be absolute paths starting with "/gitweb/"
prefix which had to be stripped, e.g. "/gitweb/static/gitweb.css".
This in turn caused web server run by "git instaweb --httpd=plackup"
to not access static files (e.g. CSS) correctly.
This is a minimal fixup, making 'plackup' web server in git-instaweb
work with default gitweb build configuration.
Reported-by: Tadeusz Sośnierz <tadzikes@gmail.com>
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
The regexp is probably too strict: qr{^/static/} should be enough,
but I didn't want to change too much at once.
This bug was not noticed because we don't have any test for
git-instaweb, not mentioning tests for all web servers supported. And
the fact that I was checking "git instaweb -httpd=plackup" against
gitweb.cgi built with custom configuration (including the fact that
GITWEB_CSS="/gitweb/static/gitweb.css").
tadzik, does that fix the issue you noticed?
Junio, could you apply this before 1.7.4? Thanks in advance.
git-instaweb.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-instaweb.sh b/git-instaweb.sh
index 10fcebb..bb57d81 100755
--- a/git-instaweb.sh
+++ b/git-instaweb.sh
@@ -549,7 +549,7 @@ my \$app = builder {
};
# serve static files, i.e. stylesheet, images, script
enable 'Static',
- path => sub { m!\.(js|css|png)\$! && s!^/gitweb/!! },
+ path => qr{^/static/.*(?:js|css|png)\$},
root => "$root/",
encoding => 'utf-8'; # encoding for 'text/plain' files
# convert CGI application to PSGI app
--
1.7.3
next prev parent reply other threads:[~2010-12-29 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 16:43 [PATCH 0/4] git-instaweb: Three fixes and one improvement Jakub Narebski
2010-12-29 16:47 ` Jakub Narebski [this message]
2010-12-29 23:24 ` [BUGFIX PATCH 1/4] git-instaweb: Fix issue with static files for 'plackup' server Junio C Hamano
2010-12-29 23:52 ` Junio C Hamano
2010-12-30 0:40 ` Jakub Narebski
2010-12-29 16:48 ` [PATCH 2/4] git-instaweb: Static files are under "static/" in gitweb_conf Jakub Narebski
2010-12-29 16:49 ` [PATCH 3/4] git-instaweb: Add checks that web server can be started and is started Jakub Narebski
2010-12-29 16:50 ` [PATCH 4/4] git-instaweb: Use "git-instaweb" as sitename (for page titles) Jakub Narebski
2010-12-30 6:23 ` Eric Wong
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=201012291747.01288.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=tadzikes@gmail.com \
/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.