You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Charlie Smith <Sm...@ldschurch.org> on 2003/06/11 22:13:22 UTC
RE: [users@httpd] Multiple httpd conf files? (New to list)
How about this for a rewrite rule?:
RewriteRule ^/(.*)$ http://%{SERVER_NAME}/%{REMOTE_USER}/$1 [R,L]
>>> support@gej-it.com 04/17/03 04:57PM >>>
Hi Denise,
Sorry it took me long time to respond, I didn't have access to my computer
for a while.
What you can do it to put redirect all subfolders to that main server and
use mod_rewrite by doing something like that, (I don't have a clue in
rewrite so ask from other members in the list here to hep with that):
Redirect /anything1 http://website.com/anything1
But in rewrite..
Joshua, can you help out here with mod_rewrite?
After you set the rewrite, then set the aliases for the clients for any
permissions that they need.
All the best,
Jeff Cohen
> -----Original Message-----
> From: Denise Mangano [mailto:DeniseM@complusdata.com]
> Sent: Tuesday, April 15, 2003 9:22 PM
> To: 'users@httpd.apache.org '
> Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
>
> Well I would need the redirect to get them from www.mywebsites.com to
> www.mywebsite.com, for example isn't that right?
>
> By using the Alias directive inside the vhost container I could make the
> alias and point it to the right directory, but I need the URL redirected
> because all SSL requests have to be served by www.mywebsite.com.
>
> Am I misunderstanding something?
>
> Thanks for your input :)
> Denise
>
> -----Original Message-----
> From: Jeff Cohen
> To: users@httpd.apache.org
> Sent: 4/15/2003 6:53 PM
> Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
>
> Man, if that's the case, then just use the alias command on each Vhost
> container, you don't need the redirection at all.
> The alias can give you that but not outside the Vhost container since
> they
> all getting a specific link that they must go to, therefore you just
> need to
> assign the right alias at the right Vhost container. Simple as is.
> All the best,
> Jeff Cohen
>
> > -----Original Message-----
> > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > Sent: Tuesday, April 15, 2003 10:33 AM
> > To: 'users@httpd.apache.org'
> > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> >
> > Unfortunately yes, each client can only have access to their own
> section
> of
> > the website. I'm dealing with government clients so it is important
> that
> > information for each client stays separated from the others.
> >
> > Basically our client will be provided with a URL to our site
> > www.mywebsite.com/client1/ where they can connect to our back end
> systems
> > through the webapp. If the go to www.mywebsite.com they will be
> prompted
> to
> > enter the URL exactly as it had been provided to them. ( I am not
> allowed
> > to post links to each subdirectory here as to not make our client list
> > available). If they know of another client and try to access
> > www.mywebsite.com/client2/ they will be brought to the index page, but
> will
> > not be able to go any further without providing information specific
> to
> the
> > intended client (controlled by the back end system).
> >
> > Thanks again,
> > Denise
> >
> >
> > -----Original Message-----
> > From: Jeff Cohen [mailto:support@gej-it.com]
> > Sent: Monday, April 14, 2003 11:03 PM
> > To: users@httpd.apache.org
> > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> >
> >
> > As I previously wrote, the alias directive *will* take effect on all
> Vhosts,
> > but the redirect will not. But let me ask you a question, does is
> really a
> > must that your clients will access only this website? Are they allowed
> to
> > access any of the other website? Are they using any of the other
> websites
> > content or just that one?
> >
> > All the best,
> > Jeff Cohen
> >
> > > -----Original Message-----
> > > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > > Sent: Monday, April 14, 2003 10:48 PM
> > > To: 'users@httpd.apache.org'
> > > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> > >
> > > Jeff,
> > >
> > > Thanks for responding. I actually didn't even think to place it
> > > outside
> > the
> > > vhost container. The only concern there is that my website will
> have
> > > a number of subdirectories - possibly over 100 (customization for
> each
> > > of
> > our
> > > clients). So since all requests have to come in through
> > > www.mywebsite.com
> > I
> > > would need redirects set up for each of these subdirectories as
> well.
> > >
> > > So for example if my live site has a subdirectory "test1" then any
> > attempts
> > > to access /test1 through the other domain names must be redirected
> to
> > > www.mywebsite.com/test1/. And so forth for each additional
> > > subdirectory.
> > If
> > > I were to place everything outside the vhost container, then I would
> > > need
> > to
> > > set up one alias for /test1/ and also one Redirect permanent /test1/
> > > http://www.mywebsite.com/test1/, and again so forth for each
> > > additional subdirectory?
> > >
> > > Is that correct? Or does it seem like mod_rewrite is a better way
> to
> > > go?
> > >
> > > Thanks again!
> > > Denise
> > >
> > >
> > > -----Original Message-----
> > > From: Jeff Cohen [mailto:support@gej-it.com]
> > > Sent: Monday, April 14, 2003 10:25 PM
> > > To: users@httpd.apache.org
> > > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> > >
> > >
> > > Hello Denise,
> > >
> > > First of all for your own knowledge, any missing detail of each and
> > > every Vhost in your conf file will be taken automatically from the
> > > Server Configuration Section, which is global for all Vhosts
> together.
> > > It means that if you'd like to have an alias /joke on all the Vhosts
> > > at once, you have to add the line for it OUTSIDE of the Vhosts
> > > containers. (e.g. Alias /joke /usr/folder/joke) - this should take
> > > effect on all Vhosts. Same
> > thing
> > > with Redirect permanent command. (e.g. Redirect permanent /joke
> > > http://yoursitename.com/hello) - in this example make sure not to
> loop
> > > the string by putting the same folder aliased in the Vhost
> container.
> > >
> > > If that doesn't help and you actually *need* the same alias to be
> > redirected
> > > then you should use mod_rewrite and Joshua can help you with that.
> :-)
> > >
> > > All the best,
> > > Jeff Cohen
> > >
> > >
> > > > -----Original Message-----
> > > > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > > > Sent: Monday, April 14, 2003 10:21 PM
> > > > To: 'users@httpd.apache.org'
> > > > Subject: [users@httpd] Multiple httpd conf files? (New to list)
> > > >
> > > > Evening everyone. I've tried searching through the archives and
> > > > reading
> > > the
> > > > FAQ's but can't seem to find a clear answer on the best way to
> > > > handle the following situation:
> > > >
> > > > I am running Apache 1.3 on RH Linux 8.
> > > >
> > > > I would like to have a website http://www.mywebsite.com allowable
> to
> > > > all. This will be my live site.
> > > >
> > > > I would also like to have a test website,
> http://test.mywebsite.com
> > > > allowable only to localhost.
> > > >
> > > > I also own 5 other domain names (www.mywebsites.com,
> > > > www.mywebsites.org, www.mywebsites.net, www.mywebsite.org,
> > > > www.mywebsite.net). However, I need to ensure all users that type
> > > > any of these by mistake get redirected to
> > > come
> > > > in through www.mywebsite.com because this is the site that I
> > > > registered my SSL certificate for.
> > > >
> > > > I am familiar with Apache enough to get this working - but I'm not
> > > > sure if
> > > I
> > > > handle it the right way. The way I am trying to do it now is
> having
> > > > one httpd.conf file in the /etc/httpd/conf directory. I set the
> > > > server name
> > > to
> > > > mywebsite.com. In my htdocs folder I have two directories:
> > > > mywebsite and test.mywebsite with aliases and permissions set in
> the
> > > > main httpd.conf. I have a series of virtual host directives set up
> > > > for the other domains to redirect to www.mywebsite.com. The only
> > > > problem with this is if my user tries to access
> > > > www.mywebsite.org/forms/ I need to redirect them to
> > > > www.mywebsite.com/forms and this can get pretty tedious if I do
> > > > this with
> > > a
> > > > bunch of redirects and aliases.
> > > >
> > > > I am wondering if I can limit what I put in that main httpd.conf
> and
> > > somehow
> > > > configure an httpd.conf file for each individual site? What would
> > > > be the best way to handle this?
> > > >
> > > > I hope I have explained this clearly. Thanks in advance for your
> > > > help. Denise
> > > >
> > > >
> --------------------------------------------------------------------
> > > > -
> > > > The official User-To-User support forum of the Apache HTTP Server
> > > > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > > > info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > > For additional commands, e-mail: users-help@httpd.apache.org
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > The official User-To-User support forum of the Apache HTTP Server
> > > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > > info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > For additional commands, e-mail: users-help@httpd.apache.org
> > >
> > >
> ---------------------------------------------------------------------
> > > The official User-To-User support forum of the Apache HTTP Server
> > > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > > info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > For additional commands, e-mail: users-help@httpd.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
> Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info. To
> > unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
> Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server
> Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
------------------------------------------------------------------------------
This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed.
==============================================================================
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: [users@httpd] Multiple httpd conf files? (New to list)
Posted by Jeff Cohen <su...@gej-it.com>.
Look at quates: :)
"But in rewrite..
Joshua, can you help out here with mod_rewrite?"
Jeff Cohen
Support@GEJ-IT.com
Tel. (416) 917-2324
www.GEJ-IT.com
GEJ-IT Networks!
> -----Original Message-----
> From: Charlie Smith [mailto:SmithCW@ldschurch.org]
> Sent: Wednesday, June 11, 2003 4:13 PM
> To: support@gej-it.com; users@httpd.apache.org
> Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
>
> How about this for a rewrite rule?:
> RewriteRule ^/(.*)$ http://%{SERVER_NAME}/%{REMOTE_USER}/$1 [R,L]
>
> >>> support@gej-it.com 04/17/03 04:57PM >>>
> Hi Denise,
> Sorry it took me long time to respond, I didn't have access to my computer
> for a while.
> What you can do it to put redirect all subfolders to that main server and
> use mod_rewrite by doing something like that, (I don't have a clue in
> rewrite so ask from other members in the list here to hep with that):
>
> Redirect /anything1 http://website.com/anything1
>
> But in rewrite..
>
> Joshua, can you help out here with mod_rewrite?
>
> After you set the rewrite, then set the aliases for the clients for any
> permissions that they need.
>
> All the best,
> Jeff Cohen
>
> > -----Original Message-----
> > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > Sent: Tuesday, April 15, 2003 9:22 PM
> > To: 'users@httpd.apache.org '
> > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> >
> > Well I would need the redirect to get them from www.mywebsites.com to
> > www.mywebsite.com, for example isn't that right?
> >
> > By using the Alias directive inside the vhost container I could make the
> > alias and point it to the right directory, but I need the URL redirected
> > because all SSL requests have to be served by www.mywebsite.com.
> >
> > Am I misunderstanding something?
> >
> > Thanks for your input :)
> > Denise
> >
> > -----Original Message-----
> > From: Jeff Cohen
> > To: users@httpd.apache.org
> > Sent: 4/15/2003 6:53 PM
> > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> >
> > Man, if that's the case, then just use the alias command on each Vhost
> > container, you don't need the redirection at all.
> > The alias can give you that but not outside the Vhost container since
> > they
> > all getting a specific link that they must go to, therefore you just
> > need to
> > assign the right alias at the right Vhost container. Simple as is.
> > All the best,
> > Jeff Cohen
> >
> > > -----Original Message-----
> > > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > > Sent: Tuesday, April 15, 2003 10:33 AM
> > > To: 'users@httpd.apache.org'
> > > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> > >
> > > Unfortunately yes, each client can only have access to their own
> > section
> > of
> > > the website. I'm dealing with government clients so it is important
> > that
> > > information for each client stays separated from the others.
> > >
> > > Basically our client will be provided with a URL to our site
> > > www.mywebsite.com/client1/ where they can connect to our back end
> > systems
> > > through the webapp. If the go to www.mywebsite.com they will be
> > prompted
> > to
> > > enter the URL exactly as it had been provided to them. ( I am not
> > allowed
> > > to post links to each subdirectory here as to not make our client list
> > > available). If they know of another client and try to access
> > > www.mywebsite.com/client2/ they will be brought to the index page, but
> > will
> > > not be able to go any further without providing information specific
> > to
> > the
> > > intended client (controlled by the back end system).
> > >
> > > Thanks again,
> > > Denise
> > >
> > >
> > > -----Original Message-----
> > > From: Jeff Cohen [mailto:support@gej-it.com]
> > > Sent: Monday, April 14, 2003 11:03 PM
> > > To: users@httpd.apache.org
> > > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> > >
> > >
> > > As I previously wrote, the alias directive *will* take effect on all
> > Vhosts,
> > > but the redirect will not. But let me ask you a question, does is
> > really a
> > > must that your clients will access only this website? Are they allowed
> > to
> > > access any of the other website? Are they using any of the other
> > websites
> > > content or just that one?
> > >
> > > All the best,
> > > Jeff Cohen
> > >
> > > > -----Original Message-----
> > > > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > > > Sent: Monday, April 14, 2003 10:48 PM
> > > > To: 'users@httpd.apache.org'
> > > > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> > > >
> > > > Jeff,
> > > >
> > > > Thanks for responding. I actually didn't even think to place it
> > > > outside
> > > the
> > > > vhost container. The only concern there is that my website will
> > have
> > > > a number of subdirectories - possibly over 100 (customization for
> > each
> > > > of
> > > our
> > > > clients). So since all requests have to come in through
> > > > www.mywebsite.com
> > > I
> > > > would need redirects set up for each of these subdirectories as
> > well.
> > > >
> > > > So for example if my live site has a subdirectory "test1" then any
> > > attempts
> > > > to access /test1 through the other domain names must be redirected
> > to
> > > > www.mywebsite.com/test1/. And so forth for each additional
> > > > subdirectory.
> > > If
> > > > I were to place everything outside the vhost container, then I would
> > > > need
> > > to
> > > > set up one alias for /test1/ and also one Redirect permanent /test1/
> > > > http://www.mywebsite.com/test1/, and again so forth for each
> > > > additional subdirectory?
> > > >
> > > > Is that correct? Or does it seem like mod_rewrite is a better way
> > to
> > > > go?
> > > >
> > > > Thanks again!
> > > > Denise
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Jeff Cohen [mailto:support@gej-it.com]
> > > > Sent: Monday, April 14, 2003 10:25 PM
> > > > To: users@httpd.apache.org
> > > > Subject: RE: [users@httpd] Multiple httpd conf files? (New to list)
> > > >
> > > >
> > > > Hello Denise,
> > > >
> > > > First of all for your own knowledge, any missing detail of each and
> > > > every Vhost in your conf file will be taken automatically from the
> > > > Server Configuration Section, which is global for all Vhosts
> > together.
> > > > It means that if you'd like to have an alias /joke on all the Vhosts
> > > > at once, you have to add the line for it OUTSIDE of the Vhosts
> > > > containers. (e.g. Alias /joke /usr/folder/joke) - this should take
> > > > effect on all Vhosts. Same
> > > thing
> > > > with Redirect permanent command. (e.g. Redirect permanent /joke
> > > > http://yoursitename.com/hello) - in this example make sure not to
> > loop
> > > > the string by putting the same folder aliased in the Vhost
> > container.
> > > >
> > > > If that doesn't help and you actually *need* the same alias to be
> > > redirected
> > > > then you should use mod_rewrite and Joshua can help you with that.
> > :-)
> > > >
> > > > All the best,
> > > > Jeff Cohen
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Denise Mangano [mailto:DeniseM@complusdata.com]
> > > > > Sent: Monday, April 14, 2003 10:21 PM
> > > > > To: 'users@httpd.apache.org'
> > > > > Subject: [users@httpd] Multiple httpd conf files? (New to list)
> > > > >
> > > > > Evening everyone. I've tried searching through the archives and
> > > > > reading
> > > > the
> > > > > FAQ's but can't seem to find a clear answer on the best way to
> > > > > handle the following situation:
> > > > >
> > > > > I am running Apache 1.3 on RH Linux 8.
> > > > >
> > > > > I would like to have a website http://www.mywebsite.com allowable
> > to
> > > > > all. This will be my live site.
> > > > >
> > > > > I would also like to have a test website,
> > http://test.mywebsite.com
> > > > > allowable only to localhost.
> > > > >
> > > > > I also own 5 other domain names (www.mywebsites.com,
> > > > > www.mywebsites.org, www.mywebsites.net, www.mywebsite.org,
> > > > > www.mywebsite.net). However, I need to ensure all users that type
> > > > > any of these by mistake get redirected to
> > > > come
> > > > > in through www.mywebsite.com because this is the site that I
> > > > > registered my SSL certificate for.
> > > > >
> > > > > I am familiar with Apache enough to get this working - but I'm not
> > > > > sure if
> > > > I
> > > > > handle it the right way. The way I am trying to do it now is
> > having
> > > > > one httpd.conf file in the /etc/httpd/conf directory. I set the
> > > > > server name
> > > > to
> > > > > mywebsite.com. In my htdocs folder I have two directories:
> > > > > mywebsite and test.mywebsite with aliases and permissions set in
> > the
> > > > > main httpd.conf. I have a series of virtual host directives set up
> > > > > for the other domains to redirect to www.mywebsite.com. The only
> > > > > problem with this is if my user tries to access
> > > > > www.mywebsite.org/forms/ I need to redirect them to
> > > > > www.mywebsite.com/forms and this can get pretty tedious if I do
> > > > > this with
> > > > a
> > > > > bunch of redirects and aliases.
> > > > >
> > > > > I am wondering if I can limit what I put in that main httpd.conf
> > and
> > > > somehow
> > > > > configure an httpd.conf file for each individual site? What would
> > > > > be the best way to handle this?
> > > > >
> > > > > I hope I have explained this clearly. Thanks in advance for your
> > > > > help. Denise
> > > > >
> > > > >
> > --------------------------------------------------------------------
> > > > > -
> > > > > The official User-To-User support forum of the Apache HTTP Server
> > > > > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > > > > info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > > > For additional commands, e-mail: users-help@httpd.apache.org
> > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > The official User-To-User support forum of the Apache HTTP Server
> > > > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > > > info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > > For additional commands, e-mail: users-help@httpd.apache.org
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > The official User-To-User support forum of the Apache HTTP Server
> > > > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > > > info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > > For additional commands, e-mail: users-help@httpd.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > The official User-To-User support forum of the Apache HTTP Server
> > Project.
> > > See <URL:http://httpd.apache.org/userslist.html> for more info. To
> > > unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > For additional commands, e-mail: users-help@httpd.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > The official User-To-User support forum of the Apache HTTP Server
> > Project.
> > > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > > For additional commands, e-mail: users-help@httpd.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
> > Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > " from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>
>
----------------------------------------------------------------------------
--
> This message may contain confidential information, and is intended only
for the
> use of the individual(s) to whom it is addressed.
>
>
> ==================================================
> ============================
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org