W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1995

Re: Getting full URI to the server

From: Jan Brittenson <bson@bugmotel.eng.sun.com>
Date: Wed, 15 Feb 1995 14:54:21 -0800
Message-Id: <199502152254.OAA03219@bugmotel.Eng.Sun.COM>
To: march@europa.com
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
   Date: Sun, 12 Feb 1995 12:50:45 -0800
   From: march@europa.com (M. Hedlund)

 > Not only is it likely, it is happening quite a bit.  There are plenty of
 > businesses buying machines and connections exclusively to put up web
 > servers, and they often want to split costs with other businesses.

It's even more complicated than that.  I have a permanent 24 h link
home over modem, and five machines home on my net.  I've set up a web
tree elsewhere, right at a T1 socket, but can't stick it into my named
database for obvious reasons.  I want to have www.homenet.com point to
it (by DNS), and have the server at the T1 socket do the right thing.
Modifying httpd to look at the header and pick the root from a config
file would be trivial, if the information were just passed.  Playing
games with IP addresses is not an option in my case, since I doubt the
T1 link owner will let me play around with their routers and interface
configurations.

Since any old Sparc-1 with 2GB disk and 32MB memory will make a
splendid server, the expensive resource is net bandwidth.  In the
future, more and more small businesses, individuals, and organizations
(the San Francisco Aids Foundation is trying to do something very
close to what I'm trying to do), will buy shares in a dedicated
off-site web server.  It'll sit right next to an existing T1 socket to
reduce telco costs

I can't see why there's even any discussion about this.  Just add the
damn field to the spec so people can get things working.

						-- Jan Brittenson
						   bson@eng.sun.com
Received on Wednesday, 15 February 1995 14:58:20 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:14 EDT