Thank you for your reply.
In '[httpd-2.4.23] mod_porxy_fdpass.la is missing', 'mod_proxy_fdpass.la
is missing' is my own comment, while comparing below messages given
during rpmbuild for each version.
[httpd-2.4.20]
Building shared: mod_proxy.la mod_proxy_connect.la mod_proxy_ftp.la
mod_pro
Thank you for your response. Yes, I use httpd's own rpm.
I just use the following command.
$rpmbuild -tb --clean httpd-2.4.23.tar.bz2
Up to httpd-2.4.20.tar.bz2, this command functioned and rpm files were
obtained without problem.
My environments:
CentOS Linux release 7.2.1511
linux kernel 3.
Hi,
Can anyone please point me to the link for the patch on 2.4.18 for
CVE-2016-1546.
Thanks
Srini
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
[httpd-2.4.23] mod_porxy_fdpass.la is missingIs this your typo or is it in your conf/build files?
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
This is a dev@ level regression, sharing with that list. Please confirm you
are using httpd's own rpm. If not, the specific --enable-modules provided
for your rpm.spec file may be at issue.
On Jul 17, 2016 3:45 AM, "kohmoto" wrote:
> I tried to rpmbuild the former version httpd-2.4.20.tar.bz2 in
I tried to rpmbuild the former version httpd-2.4.20.tar.bz2 in the same
machine. The result was successful without error. So, the rpmbuild
failure of httpd-2.4.23 missing mod_proxy_fdpass.so is not due to my
rebuild environment. All previous versions gave also successful results.
Messages outp
Hi,
It appears that mod_proxy considers a backend as failed only when
the transport layer connection to that backend fails. Is this expected?
The backends are VMs and only when I SIGSTOP the VMs, the backend is
considered in an error state and the retry= parameter has an affect.
If I've
