[14828] in SIPB bug reports
what's needed for http://www.mit.edu/sipb/ ?
daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Fri Jul 30 14:03:31 2004
From jmorzins@MIT.EDU Fri Jul 30 18:03:31 2004
Return-Path: <jmorzins@MIT.EDU>
Delivered-To: bug-sipb-mtg@CHARON.mit.edu
Received: (qmail 3676 invoked from network); 30 Jul 2004 18:03:31 -0000
Received: from biscayne-one-station.mit.edu (18.7.7.80)
by charon.mit.edu with SMTP; 30 Jul 2004 18:03:31 -0000
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])
by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i6UI2JNE016534;
Fri, 30 Jul 2004 14:02:19 -0400 (EDT)
Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73])
(authenticated bits=56)
(User authenticated as jmorzins@ATHENA.MIT.EDU)
by manawatu-mail-centre.mit.edu (8.12.4/8.12.4) with ESMTP id i6UI2HoL012015;
Fri, 30 Jul 2004 14:02:18 -0400 (EDT)
Received: (from jmorzins@localhost) by multics.mit.edu (8.12.9)
id i6UI2Ftu009593; Fri, 30 Jul 2004 14:02:15 -0400 (EDT)
Date: Fri, 30 Jul 2004 14:02:13 -0400 (EDT)
From: Jacob Morzinski <jmorzins@MIT.EDU>
To: webmaster-internal@MIT.EDU
cc: bug-sipb@MIT.EDU
Subject: what's needed for http://www.mit.edu/sipb/ ?
Message-ID: <Pine.GSO.4.55L.0407301338390.3050@multics.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hello,
Putting on my sipb locker maintainer hat, I'd like to ask the
webmasters what files are currently served underneath the path
http://www.mit.edu/sipb/
(For example, one file is /sipb/sipb.html, and this has quite a
few web pages pointing to it. We want it to continue working
in the future. What other URLs should keep working?)
I suspect that you'll want to add these files to
/afs/sipb/project/sipb , so I'm interested in knowing what
the files are, and where they'll go. Will you need to add
webmasters to the sipb locker acl, or can you use a subdirectory
of the sipb locker with a webmaster-specific acl?
Thinking about this on my own, I see two options for making the
http://www.mit.edu/sipb/* URLs still work, but would be
interested to hear suggestions if other people can think of more
solutions.
The option I prefer is to let URLs using /sipb/ do regular hesiod
lookup and point to /afs/sipb/project/sipb. We would then have to
put some WWW content into the sipb locker. I'm not excited to be
scattering *.html files around the sipb locker, but if there
aren't too many of them, it wouldn't be too bad. Future WWW files
could go into a /mit/sipb/www/ subdirectory, which would help keep
it separate from the software in the locker. This hypothetical
/mit/sipb/www subdirectory could be a separate AFS volume, have a
webmaster ACL, or have whatever makes it convenient for webmasters
who want to work with it.
The other option I can think of for making http://www/sipb/ work is
to ask the www.mit.edu maintainers to turn *OFF* hesiod expansion
for /sipb/, and to point URLs that use that path to a custom
location in AFS. Although this would maintain the purity of the
sipb locker, I dislike turning off hesiod expansion, since it
will break future people's expectations of how MIT's webservers
work.
Thanks,
-Jacob
