W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1996

Multihomed redirection servers

From: Anselm Baird_Smith <abaird@www43.inria.fr>
Date: Wed, 18 Dec 1996 09:30:54 +0100 (MET)
Message-Id: <199612180830.JAA11675@www43.inria.fr>
To: larocque@hookup.net
Cc: www-jigsaw@w3.org
Steve LaRocque writes:
 > Hi all.  I'm trying to find a memory-cheap method of accomplishing the
 > following task and need to figure out if Jigsaw will do the trick.
 > I have a web server running on a machine as "www.PARENT.com" (names
 > changed to protect the innocent! ;-).  It has its own data as well as
 > some subdirectories such as "/subsidiary1", "/subsidiary2",
 > "/subsidiary3" and so on.
 > I also have registered domain names "subsidiary1.com", "subsidiary2.com"
 > ...
 > What I'd like to do is to have "www.subsidiary1.com" map to a unique IP
 > address which is handled by Jigsaw on port 80.  When a request comes in
 > for "http://www.subsidiary1.com/dir/file", it rewrites the request and
 > issues an HTTP redirect to
 > "http://www.parent.com/subsidiary1/dir/file".  Note that I mean stemming
 > here, there is no one particular /dir/file involved.
 > I need to do this for 30 or 40 "subsidiaries".  This has elements of
 > basic URL redirection using stemming, and multihoming (IP address
 > based).
 > Anyone know if Jigsaw will do the trick?  Other ideas?

Have a look at Jigsaw's RelocateResource
(w3c.jigsaw.resources.RelocateResource). It currently doesn't handle
exactly your situation, but it's a couple lines of code to make it
work the way you want (I'll add that to the todo list).

Received on Wednesday, 18 December 1996 03:32:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:21 UTC