From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: musl 0.9.5 release and new website
Date: Sun, 16 Sep 2012 12:31:48 +0200 [thread overview]
Message-ID: <20120916103148.GK9428@port70.net> (raw)
In-Reply-To: <20120916032657.GA254@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-09-15 23:26:58 -0400]:
> Wow, thanks! I had no idea how this $PATH_INFO thing worked, but it's
> very nice. Is this thttpd-specific, or is it the generic way
> webservers work when a non-final path element is not a directory but
> instead a script? cgit is supposed to do something like this, but I
> couldn't get it to work so I hacked it to use the ugly old
> query-string style urls, but it would be a lot nicer if I could have
> just:
>
> http://git.musl-libc.org/musl/tree/README
>
the PATH_INFO is part of the cgi 1.1 rfc
http://www.ietf.org/rfc/rfc3875
most web servers can serve a vhost with a given
cgi script, i think in thttpd it's enough to
symlink the vhost name to the cgi script
it seems thttpd cgi handling has minor issues:
- it ignors the 301 status code
(and uses 302 redirects, so search engines don't
know that they should only index the target url)
(this seems to be patched on my system)
- the PATH_INFO for the root is '/.' instead of '/'
(but this is just a minor detail, and can be solved
with [ "$PATH_INFO" != /. ] || PATH_INFO=/)
so the redirect is not perfect now..
next prev parent reply other threads:[~2012-09-16 10:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 8:12 Rich Felker
2012-09-15 13:53 ` Szabolcs Nagy
2012-09-15 14:05 ` Luca Barbato
2012-09-16 3:35 ` Rich Felker
2012-09-16 3:48 ` Conrad Pankoff
2012-09-16 4:03 ` Gregor Richards
2012-09-16 11:04 ` Luca Barbato
2012-09-16 3:26 ` Rich Felker
2012-09-16 10:31 ` Szabolcs Nagy [this message]
2012-09-16 12:39 ` Rich Felker
2012-09-16 3:29 ` Rich Felker
2012-09-16 21:42 ` Szabolcs Nagy
2012-09-17 3:02 ` Rich Felker
2012-09-17 7:35 ` Szabolcs Nagy
2012-09-18 13:56 ` Rich Felker
2012-09-15 23:09 ` Isaac Dunham
2012-09-16 3:41 ` Rich Felker
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=20120916103148.GK9428@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).