From: Eric Grosse <ehg@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] httpd and magic
Date: Thu, 14 Nov 2002 10:11:33 -0500 [thread overview]
Message-ID: <61596701780d20c7acb50409fc75ab6d@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
Correct, it sounds like you do need a modified httpd. After recognizing
"/magic" and before doing the execl(), it would use the supplied Host:
header line to select a new namespace.
[-- Attachment #2: Type: message/rfc822, Size: 2244 bytes --]
From: Moroo Jun <jun@moroo.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] httpd and magic
Date: Thu, 14 Nov 2002 22:50:14 +0900
Message-ID: <00BAE13C-F7D8-11D6-86F1-0050E4504768@moroo.com>
On 2002.11.14, at 01:12, Eric Grosse wrote:
> Did you get a satisfactory solution to having /magic/somecgi
> behavior depend on the domain name?
Not yet.
Maybe I should modify httpd for this purpose.
I tried to use plan9 for hosting service OS. I should treat hosting
service user as a computer beginner.
I afraid the following situation.
User A(his domain is domain1.org) creates cgi "somecgi" and user B(his
domain is domain2.org) create same name "somecgi" cgi but different
program.
next reply other threads:[~2002-11-14 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 15:11 Eric Grosse [this message]
2002-11-14 15:55 ` Gabriel Diaz Lopez de la Llave
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 16:12 Eric Grosse
2002-11-14 13:50 ` Moroo Jun
2002-10-30 2:04 YAMANASHI Takeshi
2002-10-30 14:11 ` Moroo Jun
2002-10-29 15:48 Moroo Jun
2002-10-30 9:14 ` matt
2002-10-30 14:41 ` Moroo Jun
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=61596701780d20c7acb50409fc75ab6d@plan9.bell-labs.com \
--to=ehg@research.bell-labs.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).