Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread Eric Covener
On Fri, Feb 6, 2015 at 7:18 PM, mahendra babu wrote: > In one of the apache instance (2.2.3 version 64-bit) we got cache issue and > you had confirmed that caches issues were fixed in 2.2.13 and suggested to > use latest 2.2.29. > > In one of the other apache instances (2.2.11 version 32-bit) we d

Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread Eric Covener
On Fri, Feb 6, 2015 at 7:18 PM, mahendra babu wrote: > So we would like to understand what version of apache 32-bit the cache issue > were fixed? There's only one codebase. 99+% of bugs the architecture (32-bit, 64-bit) is irrelevant. -

Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread mahendra babu
Hi Eric, I apologize for any confusion. To be precise, our deployment has several apache instances of different versions including 32-bit and 64-bit versions. In one of the apache instance (2.2.3 version 64-bit) we got cache issue and you had confirmed that caches issues were fixed in 2.2.13 and

Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread Eric Covener
On Fri, Feb 6, 2015 at 4:41 PM, mahendra babu wrote: > Thanks for the reply. You had confirmed that cache bugs was fixed in 2.2.13 > for 64-bit Apache version. We had another apache instance of 2.2.11 but it > is 32-bit. So the question is which Apache version fixed the mod_cache issue > in 32 bit

Re: [users@httpd] what's the minimum version of openssl required by 2.2.29?

2015-02-06 Thread Shane Witbeck
Daniel, Thanks for the helpful reply. After reading it I realized that I’m indeed compiling on a system that’s different than the runtime which led to my issue. In my case, apache was compiled with latest CentOS with a newer openssl version. The runtime was an older version of CentOS with an o

[users@httpd] SSL Not Allowing Access to Site

2015-02-06 Thread Chris Arnold
Apache 2.4.10 on SLES12. Apache 2.4.10 reverse proxy facing the internet that "proxies" https requests to webapp on a different server on the same LAN. Trying to "proxy" https://example.com/folder. This works in apache 2.2.12: ProxyPass /ifolder https://example.com/folder ProxyPassReverse /ifol

Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread mahendra babu
Hi Eric and Yehuda, Thanks for the reply. You had confirmed that cache bugs was fixed in 2.2.13 for 64-bit Apache version. We had another apache instance of 2.2.11 but it is 32-bit. So the question is which Apache version fixed the mod_cache issue in *32 bit apache* , may be this issue was fixed i

Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread Yehuda Katz
Are you asking if you should update your 2.2.11 servers too or are you asking what is the oldest version you could update to and still resolve the problem? I would guess that almost everyone here will tell you to upgrade to the newest version on all your systems. Older versions may have security is

Re: [users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread Eric Covener
On Fri, Feb 6, 2015 at 3:35 PM, mahendra babu wrote: > Before we would recommend our applications teams to use specific apache > server with mod_cache enabled, we would like to know which specific base > version of Apache has all mod_cache fixes? The changelog says _a_ mod_cache bug was fixed in

[users@httpd] mod_cache fixed in which Apache version?

2015-02-06 Thread mahendra babu
Hi, We'd filed a bug 57538 with Apache few days ago where we had impersonation issue using mod_cache in Apache 2.2.3 64-bit version. We got reply from Apache that mod_cache bugs was fixed in 2.2.13 version and they recommended to use latest 2.2.29. In our environment, there are many more other a

[users@httpd] Require IP range issue Apache 2.4

2015-02-06 Thread Marcello Lorenzi
Hi All, I experienced a strange issue on Apache 2.4.3 installed on a CentOS server. To deny the access to a internal page I put this configuration : Require all denied Require ip xxx.xxx.xxx This configuration has to permit the access from an external IP range but it's not working.