From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] web server
Date: Sun, 19 Apr 2009 13:05:21 -0400 [thread overview]
Message-ID: <e4fac1dfcdcca4308afbd9da4b98047b@quanstro.net> (raw)
In-Reply-To: <97a49263e0b4c855f2f2a42975a9b8bc@9netics.com>
On Sun Apr 19 12:03:54 EDT 2009, 9nut@9netics.com wrote:
> you could make local mods to your httpd so that paths starting with
> /cgi are given similar treatment as those that start with /magic; it
> would execute "cgi" and pass it the arguments as usual. then url is:
>
> http://myserver/cgi/foo?var1=1&var2=2
>
> and in script "foo" the $QUERY_STRING will be "var1=1&var2=2"
if you look at /sys/src/cmd/ip/httpd/init.c you'll see that
argv[3] is the query string.
minooka; g req.search init.c
init.c:97: connect.req.search = argv[3];
there has been some recent reorganization of httpd.c
that i haven't carefully looked at.
about the same time i made a few modifications of my
own to eliminate some bad interactions between magic,
@ and other redirections. i don't recall the senerio
exactly, but depending on the situation, arguments
could be parsed or not parsed.
if anyone else needs that, i'd be glad to put it on sources.
- erik
next prev parent reply other threads:[~2009-04-19 17:05 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 16:10 Rudolf Sykora
2009-04-16 16:16 ` erik quanstrom
2009-04-18 17:19 ` Enrico Weigelt
2009-04-26 21:43 ` Roman V. Shaposhnik
2009-04-16 16:18 ` Devon H. O'Dell
2009-04-16 16:22 ` Rudolf Sykora
2009-04-16 16:26 ` erik quanstrom
2009-04-16 17:22 ` [9fans] Rails? (was Re: web server) Pietro Gagliardi
2009-04-16 17:41 ` hiro
2009-04-16 17:50 ` Devon H. O'Dell
2009-04-16 18:19 ` Pietro Gagliardi
2009-04-16 18:51 ` erik quanstrom
2009-04-17 19:46 ` Tom Lieber
2009-04-16 17:58 ` Jack Johnson
2009-04-17 11:54 ` [9fans] web server maht
2009-04-17 12:02 ` Rudolf Sykora
2009-04-26 21:59 ` Roman V. Shaposhnik
2009-04-27 11:16 ` Uriel
2009-04-27 17:35 ` maht
2009-04-27 17:53 ` erik quanstrom
2009-04-28 18:36 ` maht
2009-04-17 12:31 ` Uriel
2009-04-17 12:45 ` Rudolf Sykora
2009-04-17 12:51 ` Devon H. O'Dell
2009-04-17 13:53 ` maht
2009-04-17 14:07 ` Rudolf Sykora
2009-04-18 22:16 ` Uriel
2009-04-18 22:31 ` john
2009-04-18 23:00 ` Uriel
2009-04-19 0:59 ` john
2009-04-19 6:57 ` Steve Simon
2009-04-19 11:52 ` erik quanstrom
2009-04-19 13:10 ` john
2009-04-19 13:38 ` erik quanstrom
2009-04-19 16:02 ` Skip Tavakkolian
2009-04-19 17:05 ` erik quanstrom [this message]
2009-04-19 22:02 ` Federico G. Benavento
2009-04-19 23:21 ` erik quanstrom
2009-04-20 0:05 ` Federico G. Benavento
2009-04-20 1:42 ` Skip Tavakkolian
2009-04-20 2:04 ` erik quanstrom
2009-04-20 16:17 ` maht
2009-04-17 13:22 ` erik quanstrom
2009-04-18 22:13 ` Uriel
2009-04-18 22:27 ` erik quanstrom
2009-04-18 22:56 ` Uriel
2009-04-19 0:45 ` erik quanstrom
2009-04-26 22:08 ` Roman V. Shaposhnik
2009-04-26 22:34 ` hiro
2009-04-27 12:03 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2000-12-18 12:08 [9fans] Web Server forsyth
2000-12-18 10:02 thedesertfox95
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=e4fac1dfcdcca4308afbd9da4b98047b@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).