Re: [users@httpd] 2 server certificates

2014-12-23 Thread daniel bryan
It sounds like you have 1 website, and you want to make sure both public users, and LAN users can see the content. I think it's best to do as Jason suggested an use the public hostname as the CN, and do a subject alt DNS name of the server.lan or you could create DNS records in your lan to resolve

[users@httpd] PHP proxy loop

2014-12-23 Thread Henrik Hudson
So, this bug was submitted awhile ago, but doesn't seem to have any traction. Is it perhaps a mis-config or a way around this issue? https://issues.apache.org/bugzilla/show_bug.cgi?id=55415 Basically, if you do: ProxyErrorOverride On ProxyPassMatch to send PHP files to php-fpm and then set Error

Re: [users@httpd] Apache 2.4 create a huge amount of shared memory segments

2014-12-23 Thread Jim Jagielski
If migrating to 2.4, I would suggest using the method Yann describes and have each balancer defined in its own vhost section. This is because it is most likely that inheriting balancers will be deprecated/removed in later versions of httpd, simply because (1) it doesn't make sense and (2) causes th

Re: [users@httpd] Apache 2.4 create a huge amount of shared memory segments

2014-12-23 Thread Jim Jagielski
So is the main issue the amount of shm used, right? > On Dec 19, 2014, at 5:04 AM, Sylvain Goulmy wrote: > > Hi Yann, > > Thank you for your feedback. > > My configuration is currently defining 338 virtual hosts and 169 proxy > balancers. > > The balancers are defined in the main section. Ea

RE: [users@httpd] 2 server certificates

2014-12-23 Thread Jason Pyeron
> -Original Message- > From: MM > Sent: Tuesday, December 23, 2014 8:30 > > Hello, > > My network connectivity looks like: > > setting 1 > laptop -> corpfirewall -> ... -> homefirewall -> > serverbox (httpd 2.4) > in this setting, i have a public dns registered hostname > autou

[users@httpd] 2 server certificates

2014-12-23 Thread MM
Hello, My network connectivity looks like: setting 1 laptop -> corpfirewall -> ... -> homefirewall -> serverbox (httpd 2.4) in this setting, i have a public dns registered hostname autoupdated by my ISP. my homefirewall forwards all traffic https to serverbox. setting 2 samelaptop -> sam