[14830] in SIPB bug reports
Re: what's needed for http://www.mit.edu/sipb/ ?
daemon@ATHENA.MIT.EDU (Alex Rolfe)
Fri Jul 30 14:20:13 2004
From arolfe@MIT.EDU Fri Jul 30 18:20:12 2004
Return-Path: <arolfe@MIT.EDU>
Delivered-To: bug-sipb-mtg@CHARON.MIT.EDU
Received: (qmail 4300 invoked from network); 30 Jul 2004 18:20:12 -0000
Received: from biscayne-one-station.mit.edu (18.7.7.80)
by charon.mit.edu with SMTP; 30 Jul 2004 18:20:12 -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 i6UIJjVx021231;
Fri, 30 Jul 2004 14:19:45 -0400 (EDT)
Received: from metacircular-evaluator.mit.edu (METACIRCULAR-EVALUATOR.MIT.EDU [18.243.1.191])
(authenticated bits=56)
(User authenticated as arolfe@ATHENA.MIT.EDU)
by manawatu-mail-centre.mit.edu (8.12.4/8.12.4) with ESMTP id i6UIJjoM013020
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 30 Jul 2004 14:19:45 -0400 (EDT)
Received: (from arolfe@localhost) by metacircular-evaluator.mit.edu (8.12.9)
id i6UIJjUh027077; Fri, 30 Jul 2004 14:19:45 -0400
To: Jacob Morzinski <jmorzins@mit.edu>
Cc: webmaster-internal@mit.edu, bug-sipb@mit.edu
Subject: Re: what's needed for http://www.mit.edu/sipb/ ?
References: <Pine.GSO.4.55L.0407301338390.3050@multics.mit.edu>
From: Alex Rolfe <arolfe@MIT.EDU>
Date: Fri, 30 Jul 2004 14:19:45 -0400
In-Reply-To: <Pine.GSO.4.55L.0407301338390.3050@multics.mit.edu> (Jacob
Morzinski's message of "Fri, 30 Jul 2004 14:02:13 -0400 (EDT)")
Message-ID: <ubz3c39pdby.fsf@metacircular-evaluator.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Currently, www.mit.edu/sipb serves content from
/afs/sipb/project/www/root/sipb.
I'd suggest that the easiest option is a symlink in AFS from the
relevant places in the sipb locker to project/www/root. This lets
webmasters edit the content without changing SIPB locker ACLs and
doesn't add significantly to the complexity of anything else.
Alex
Jacob Morzinski <jmorzins@MIT.EDU> writes:
> 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
