From: john at keeping.me.uk (John Keeping)
Subject: Troubles using special characters in links with lighttpd
Date: Fri, 15 May 2015 13:24:29 +0100 [thread overview]
Message-ID: <20150515122429.GD10518@serenity.lan> (raw)
In-Reply-To: <1431691703.5085.4.camel@gmail.com>
On Fri, May 15, 2015 at 02:08:23PM +0200, David Demelier wrote:
> I'm trying to setup cgit with lighttpd, this is my actual
> configuration :
>
> $HTTP["host"] == "git.malikania.fr" {
> alias.url = (
> "/static/" => "/usr/local/www/cgit/",
> "/cgit.cgi" => "/usr/local/www/cgit/cgit.cgi",
> )
> url.rewrite-once =
> (
> "^/static/.*$" => "$0",
> "^/([^?/]+/[^?]*)?(?:\?(.*))?$" => "/cgit.cgi?url=$1&
> $2",
> )
> server.document-root = "/usr/local/www/cgit"
> cgi.assign = ( ".cgi" => "/usr/local/www/cgit/cgit.cgi" )
> }
>
>
> I have found several documents about that, this is mainly written from
> [1].
>
> Almost everythin works, except directories that contains special
> characters that should be escaped. For example, I have a directory named
> "C++", and this one will not work from the rewrite rule:
>
> http://git.malikania.fr/code/tree/
>
> If you click on C++, you get an empty directory, however, the resolved
> link with appropriate characters works fine:
>
> http://git.malikania.fr/code/tree/C%2b%2b
>
> I have no idea how to fix that, is it a lighttpd problem or a cgit
> configuration missing?
I think CGit should be encoding the '+' in the path here, but according
to [1] that isn't required in the path element of a URL, so something
else must be wrong.
The patch below should cause CGit to escape the '+', but I haven't had
time to analyze the full implications, so I'm not sure if it will break
anything else (a cursory look suggests it will be OK but I want to spend
a bit more time examining all the callers before sending a proper
patch).
[1] http://blog.lunatech.com/2009/02/03/what-every-web-developer-must-know-about-url-encoding
-- >8 --
diff --git a/html.c b/html.c
index 155cde5..c61db1c 100644
--- a/html.c
+++ b/html.c
@@ -222,7 +222,7 @@ void html_url_path(const char *txt)
while (t && *t) {
unsigned char c = *t;
const char *e = url_escape_table[c];
- if (e && c != '+' && c != '&') {
+ if (e && c != '&') {
html_raw(txt, t - txt);
html(e);
txt = t + 1;
next prev parent reply other threads:[~2015-05-15 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 12:08 demelier.david
2015-05-15 12:24 ` john [this message]
2015-05-15 12:39 ` john
2015-05-15 13:12 ` demelier.david
2015-05-15 13:32 `
2015-05-15 13:34 ` john
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=20150515122429.GD10518@serenity.lan \
--to=cgit@lists.zx2c4.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 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).