RE: [cobalt-users] Get Rid of Public Qube2 Page

["Eric" <eric@xxxxxxxxxx>]

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Rod Todd
Sent: Tuesday, September 05, 2000 5:40 PM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: [cobalt-users] Get Rid of Public Qube2 Page


Hello.  Has anyone found a way to make the Qube2
"public site" ("www.yourdomain.com/cobalt/")fully
inaccessible to the public, since we do not want the
world or users being able to browse other user's email
addresses, usernames, and "private" web pages.
Cheers,
RT

>>>>
here is what "happened" on my qube, and it sorta did what you want, although
I didn't intend for if to do this.

I replaced the index.html file in home/groups/home with the template I
preferred, which removed getting the public site when accessing the domain
for the main server.
It was still available at mydomain.com/cobalt.
I then added several virtual domains, using the NameVirtualHost directive
for the Qube's only IP, and naming the virtualhosts by domain name in
VirtualHost Directives following the NameVirtualHosts directive in the
httpd.conf file.  I included the name of the server "mydomain.com" as a
virtual host, with document root at home/groups/home.  Now when you access
the Qube via mydomain.com, you get directed as a virtual host, rather than
the main IP address.  You can see the public site if you add the /cobalt/ to
the URL, or the IP address, but the GUI cant link the icons so you can't
really read the table correctly, and when you try to go to a users site via
the Users list in the table, it prepends a .user/users/username to the link,
which won't take you anywhere. Granted, if you delete the .user/ prependage,
you get there, but you have to know to do that.  I didn't really want this
to happen, but with out specifying the mydomain.com as a VirtualHost, the
server would default to the first VirtualHost in the list, and not resolve
to home/groups/home/index.html at all.  Even with mydomain.com specified as
at Virtual Host, if it isn't the first one in the list, the IP will resolve
to whichever virtualhost is first in the list.

This also breaks the Admin site, so that you have to specify the secure port
to get to it ( www.domain.com:xx/.cobalt/sysManage/)  It works fine as long
as you request it that way.

I know this doesn't really answer your question directly, but my point is
that, by directing the Qubes main domain as a virtual host, you compromise
the cobalt GUI systems ability to append and prepend relative links, and it
will essentially break the link system. It may provide a clue how to disable
the system as you are seeking to do.

If anybody has a solution how to fix my problem ( I'd like to have
mydomain.com automatically to home/groups/home like it does when there are
no virtualHosts defined, and still be able to use the Public site, and not
have to specify the port to get to Admin site)  Please let me know.  I've
searched the KB and Archives, and am still searching, but no luck so far.

Eric R. Lewis
ErixIS
2585 Bell Road
Montgomery, AL  36117
eric@xxxxxxxxxx
www.erixis.com