Re: [TCLUG:4274] Apache; httpd.conf, virtual host and ...

[rtp <rtp@iaxs.net>]

Sandipan,

The srm.conf definitely clarified mapping users root directory and files.

I am going to work on the frameset issue more today. Basically a client
request for http://kronkass.com should open in the mi-recordz.com frame set
rather than opening it's pages outside of the Mi-Recordz frame set.  I don't
want the band webs to be seperate from mi-recordz when they're called by FQDN
from a client browser.

Thanks much for the srm.conf tip, Mi-Recordz is another step closer.

ron parker


Sandipan Panigrahi wrote:

> 1. When you are defining frames give each frame a name.
>    e.g.
> <FRAMESET .... >
> <FRAME NAME="index_frame" SRC="index.html"....>
> <FRAME NAME="body_frame" SRC="body.html" .....>
> </FRAMESET>
>
> then when you have links you can specify the "TARGET" field to
> make it go to a particular frame. e.g. in index.html if you
> want to load http://kronkass.com/ you can do a
> <A HREF="http://kronkass.com" TARGET="body_frame"> to make it
> load in the "body" frame that you created.
>
> The TARGET will also take other values such as TARGET="blank"
> which will create a new blank window and load it up.
>
> "self" will load it in the frame that the href is on.
> "parent" will load it to the parent.
> "top" will load it on the complete window.
>
> 2. The way I use the ~user field is by setting the
>         "UserDir" parameter in
>         /etc/httpd/conf/srm.conf
>    to a directory "www" and then creating a directory called "www"
>    under each users home directory which becomes the document
>    root dir for that user.
>
> Hope this helps.
> --
> sandipan
>
> rtp wrote:
> >
> > My business www.mi-recordz.com sells band products over the internet.
> > I've built a web that uses a frame set to trap my customer pages. I've
> > included the virtual host entries for the mi-recordz.com (my business)
> > and kronkass.com (one of my customers).
> >
> > I have three questions:
> >
> > 1. What directive would I use to tell www.kronkass.com to open in the
> > www.mi-recordz.com frameset? That is the frame in which it would open if
> > a client browser requested the document from within the mi-recordz.com
> > web by selecting an <a href...> link. I guess the other half of this
> > issue is I need to release a client browser when they request a document
> > which isn't part of the mi-record.com web.
> >
> > 2. Because I'll have customers that don't have a FQDN I need to open
> > their pages from their home directories, "www.mi-recordz.com/~bandname".
> > Where "~bandname" is the user account name which refers to a set of
> > documents that the respective band has rwx access to which is the
> > typical ISP scenario.  I've currently got a link from www.mi-recordz.com
> > | Bandz | DaBigNevaWas which when selected results in "Not Found The
> > requested URL /~dabign was not found on this server." Is this simply a
> > matter of including the path to the document or is "~" a referring
> > character that I can use?
> >
> > 3. Is DocumentRoot the users home directory and the subdirectories
> > leading to the html documents? As I ask this question it seems painfully
> > obvious that it is. Oh well, such are the woes of learning.
> >
> > NameVirtualHost 209.134.131.41
> >
> >     <VirtualHost 209.134.131.41>
> >     ServerAdmin rtp@mi-recordz.com
> >     ServerName www.mi-recordz.com
> >     DocumentRoot /home/mi-r/www/html
> >     #DocumentRoot /www/domain
> >     ErrorLog logs/mi-recordz.com-error_log
> >     TransferLog logs/mi-recordz.com-access_log
> >     </VirtualHost>
> >
> >     <VirtualHost 209.134.131.41>
> >     ServerAdmin mi-r@mi-recordz.com
> >     ServerName www.kronkass.com
> >     DocumentRoot /home/kronk/www/html
> >     #DocumentRoot /www/otherdomain
> >     ErrorLog logs/mi-recordz.com-error_log
> >     TransferLog logs/mi-recordz.com-access_log
> >     </VirtualHost>
> >
> > I hope my questions are stated clearly enough to be understood. If not,
> > please request that I clarify.
> >
> > Thanks in advance
> >
> > ron parker
> > 374-2578
> > ~
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tclug-list-unsubscribe@listserv.real-time.com
> > For additional commands, e-mail: tclug-list-help@listserv.real-time.com
> > Try our website: http://tclug.real-time.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@listserv.real-time.com
> For additional commands, e-mail: tclug-list-help@listserv.real-time.com
> Try our website: http://tclug.real-time.com