[users@httpd] require ip range limits

Are there any known limits to the number of IP ranges in a require not statement in 2.4.x? eg: require not 1.1.1.x 1.1.4.x 1.1.5.x 1.1.9.x 2.0.0.x and so forth, an ACL I'm consider using on a customers site at their request would mean around 119 IP ranges :- Just wonder if that hits any

[users@httpd] VirtualHost configuration not working as expected with ePages solution

Hi I have a Centos server running ePages (which runs on Apache). Now I want to use the same server to host a couple of other sites as well, but I can't seem to get my configs working correctly. I'm not sure if anyone is familiar with epages (I've looked on their forums to no avail), but this is

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

What Apache version are you running? Have you added something like below in httpd.conf NameVirtualHost your_ip_address:80 then VirtualHost your_ip_address:80 DocumentRoot /var/www/html/path ServerName another.url.com ServerAlias another.url.com /VirtualHost Replace your_ip_address with the

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

Hi, and thanks for your reply Server version: Apache/2.2.3 Server built:   Jan  5 2012 13:05:41 And yes, I have put in the NameVirtualHost as below: NameVirtualHost *:80 I have tried many different permutations of settings but never seem to get the expected result, it will either always go

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

VirtualHost _default_:80 VirtualHost my.ip.add.res:80 These have to be the identicalvalues for name-based vhosts to treat them as part of a set. If you don't care what IP address is used, use *:80 for both. If you do care, use t my.ip.add.res:80 for both. NameVirtualHost should have again an

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

Hi I have changed both VirtualHost definitions to *:80 and NameVirtualHost has the same, however both whichever hostname I use I still get the same site. Does it matter that the VirtualHost definitions are in separate config files? Thanks again From: Eric

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

Just to clarify, this is how the conf files look now: httpd.conf: NameVirtualHost *:80 VirtualHost *:80 DocumentRoot /var/www/html/path/ ServerName url2.mydomain.com ServerAlias url2.mydomain.com /VirtualHost epages.conf: IfDefine PROXY VirtualHost *:80 ServerName url1.mydomain.com

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

On Thu, Jan 3, 2013 at 9:01 AM, Tom Frost fro5...@yahoo.com wrote: Just to clarify, this is how the conf files look now: httpd.conf: NameVirtualHost *:80 VirtualHost *:80 DocumentRoot /var/www/html/path/ ServerName url2.mydomain.com ServerAlias url2.mydomain.com /VirtualHost

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

On Thu, Jan 3, 2013 at 8:58 AM, Tom Frost fro5...@yahoo.com wrote: Hi I have changed both VirtualHost definitions to *:80 and NameVirtualHost has the same, however both whichever hostname I use I still get the same site. Does it matter that the VirtualHost definitions are in separate config

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

If I use either url1.mydomain.com or url2.mydomain.com they both go to the url2.mydomain.com VirtualHost site. I have cleared caches and done a Ctrl-F5 to force the page to reload.  I'm sure that its something to do with epages, as I said there is a lot of other config in there but I'm

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

Tom, I'd be curious what the output of your 'apachectl -t -D DUMP_VHOSTS' looks like? I've come across this problem as well in a related degree, and interrogating the output of the 'DUMP_VHOSTS' above will at least tell you the top-to-bottom order your vhost requests will travel down in

Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution

On 04/01/2013 1:02 AM, Tom Frost fro5...@yahoo.com wrote: Just to clarify, this is how the conf files look now: httpd.conf: NameVirtualHost *:80 VirtualHost *:80 DocumentRoot /var/www/html/path/ ServerName url2.mydomain.com ServerAlias url2.mydomain.com /VirtualHost epages.conf: