Re: [users@httpd] Persistent proxied connections with Apache 2.4.x?

> I am wondering if there is a way to do this (make all the backend connections > persistent with the "Connection: keepalive")? IMO there's no way to do it without enumerating all your backend hosts. Apache needs to create a separate worker for each host at startup time. > "Connection: keepali

[users@httpd] mod_cache_disk: .header and strange Vary: User-Agent

I recently received a dozens of AH00708: errors in my logs. Example: > (2)No such file or directory: AH00708: Cannot open data file > /var/cache/apache2/mod_cache_disk/Y/Z/CLVvRR_4nNWabdUv_5wA.header.vary/B/z/b...@34pw3mjoqhrzda2kq.data Said file does not exist, only does the corresponding .heade

[users@httpd] Configure a Forward Proxy that inspect client certificate

Hi, I've configured a forward proxy by enabling the "ProxyRequests" switch in the mod_proxy module. It forwards client traffic to origin server perfectly. But we have a requirement (for security purpose) that we need to inspect TLS handshake between the client and server. To be specific, following

[users@httpd] Persistent proxied connections with Apache 2.4.x?

Hi, We want to use Apache 2.4.x to proxy through to some SharePoint instances using NTLM logins.  From testing, it looks like the Apache-to-SharePoint connections need to be persistent, with "Connection: keepalive" in the request headers going from Apache-to-SharePoint. We can do this using a di

Re: [users@httpd] pcre.h missing during apache installation, should be replaced by pcre2.h ?

Hello Doyle, I suspect that pcre2 is not yet supported by Apache httpd. Thanks, Mike Rumph On 10/7/2015 8:52 AM, Doyle Jonathan wrote: Yes, although I’m not sure about the exact path. My source distributions are at /Users/ewandelanoy/Documents/Installers/ My installed stuff are at /User

[users@httpd] New Hardware Causing Apache Cert Error ERR_SSL_PROTOCOL_ERROR

Hello. I am running Apache 2.2.29 and Tomcat 7.0.64 with tomcat connector(mod_jk) version 1.2.41 on AIX version 7.1 server. We are trying upgrade the hardware and just move the LPAR(VM) to a new machine. The new hardware has the same IP address and hostname. Of course the old machine is shut

Re: [users@httpd] Common configuration-set for all VirtualHost's

mod_macro works pretty well On 10/22/15 3:11 AM, "Yann Ylavic" wrote: >On Thu, Oct 22, 2015 at 12:05 AM, Binyamin <7rai...@inbox.lv> wrote: >> >> Does Apache (httpd) has compatibility to define configuration-set for >>all >> VirtualHost's like: > >You can have a look at mod_macro: >https://httpd

Re: [users@httpd] Common configuration-set for all VirtualHost's

On Thu, Oct 22, 2015 at 12:05 AM, Binyamin <7rai...@inbox.lv> wrote: > > Does Apache (httpd) has compatibility to define configuration-set for all > VirtualHost's like: You can have a look at mod_macro: https://httpd.apache.org/docs/2.4/mod/mod_macro.html. Regards, Yann.