Re: [users@httpd] suspicious proxy(?) URLs in logs

2011-03-13 Thread Jeroen Geilman
On 03/13/2011 01:53 AM, Eric Covener wrote: On Thu, Mar 10, 2011 at 8:16 AM, Rob De Langhe wrote: hi, while going occasionally through the access logs of a 2.2.17 Apache server, I noticed some URLs of remote locations where my server would have made a GET for ?! an example: 194.0.122.13

[users@httpd] SSL Directives

2011-03-13 Thread Hossy
I'm seeking validation on an issue I'm discussing regarding the use of the SSLCACertificateFile and SSLCertificateChainFile directives. What I'm trying to do: Install an SSL certificate on my web site (for use with HTTPS) and provide the certificate chain from the server. What I'm not trying to do

[users@httpd] Virtual Host Directory Permissions Problem

2011-03-13 Thread Dennis Putnam
I am setting up a new virtual host and am having trouble with the root directory. My new virtual host document root (/var/www/html/vhroot) is a child directory of my primary host root (/var/www/html). Is it legal to do that? When I try to access my new virtual host, I get the index from the primary

RE: [users@httpd] Virtual Host Directory Permissions Problem

2011-03-13 Thread Hossy
1. What are you typing to access it? 2. Try removing the ":443" from your primary ServerName entry. I believe the port is defined inside the tag. -Original Message- From: Dennis Putnam [mailto:d...@bellsouth.net] Sent: Sunday, March 13, 2011 1:27 PM To: users@httpd.apache.org Subject: [

[users@httpd] multiple apache instances with mod_jk or mod_proxy - bind to virtual interface

2011-03-13 Thread Dirk Schaare
Dear all, we would like to run multiple Apache 2.2 instances as frontend / proxy to separate concerns of different applications and clients. The idea was to run a separate Apache configured to listen exclusively on a virtual interface, e.g eth1:10, eth0:11, etc. for each Tomcat backend server.

Re: [users@httpd] Virtual Host Directory Permissions Problem

2011-03-13 Thread Francois Gingras
On Sun, Mar 13, 2011 at 4:59 PM, Hossy wrote: > 1. What are you typing to access it? > 2. Try removing the ":443" from your primary ServerName entry.  I believe > the port is defined inside the tag. > > -Original Message- > From: Dennis Putnam [mailto:d...@bellsouth.net] > Sent: Sunday, M