9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Moroo Jun <moroo@nifty.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] httpd and magic
Date: Wed, 30 Oct 2002 23:41:27 +0900	[thread overview]
Message-ID: <ABD14760-EC15-11D6-9A27-0050E4504768@nifty.com> (raw)
In-Reply-To: <009f01c27ff4$c7d8fef0$6501a8c0@KIKE>

On 2002.10.30, at 18:14, matt wrote:
> You could write a script that mux's the requests and execs the correct
> script

Yes. but in this case I have to know cgi program name.

One solution is that I change httpd to Pegasus.
Or bind cgi directory (for example /usr/domain1/bin/ip) on /bin/ip/httpd
each access.



  reply	other threads:[~2002-10-30 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 15:48 Moroo Jun
2002-10-30  9:14 ` matt
2002-10-30 14:41   ` Moroo Jun [this message]
2002-10-30  2:04 YAMANASHI Takeshi
2002-10-30 14:11 ` Moroo Jun
2002-11-13 16:12 Eric Grosse
2002-11-14 13:50 ` Moroo Jun
2002-11-14 15:11 Eric Grosse
2002-11-14 15:55 ` Gabriel Diaz Lopez de la Llave

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=ABD14760-EC15-11D6-9A27-0050E4504768@nifty.com \
    --to=moroo@nifty.com \
    --cc=9fans@cse.psu.edu \
    /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).