[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61179

--- Comment #8 from Donatas Abraitis  ---
The latest patch works as expected:

root@donatas-laptop:/home/donatas/httpd-2.4.43# grep TTLimit
/usr/local/apache2/conf/httpd.conf 
TTLimit 5
root@donatas-laptop:/home/donatas/httpd-2.4.43# strace -esetsockopt
/usr/local/apache2/bin/httpd -f /usr/local/apache2/conf/httpd.conf 
setsockopt(3, SOL_SOCKET, SO_REUSEPORT, [1], 4) = 0
setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
setsockopt(4, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
setsockopt(4, SOL_IPV6, IPV6_V6ONLY, [0], 4) = 0
setsockopt(4, SOL_SOCKET, SO_SNDBUF, [1024], 4) = 0
setsockopt(4, SOL_TCP, TCP_NODELAY, [1], 4) = 0
setsockopt(4, SOL_IP, IP_TTL, [5], 4)   = 0
setsockopt(4, SOL_TCP, TCP_DEFER_ACCEPT, [30], 4) = 0
+++ exited with 1 +++
root@donatas-laptop:/home/donatas/httpd-2.4.43#

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61179

Donatas Abraitis  changed:

   What|Removed |Added

  Attachment #37265|0   |1
is obsolete||

--- Comment #7 from Donatas Abraitis  ---
Created attachment 37267
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37267=edit
TTLimit.patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 61090] mod_proxy gives 502 on early HTTP response (3xx, 4xx, 5xx)

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61090

--- Comment #20 from Michael Osipov  ---
I could now recreate the failure from mod_proxy_http with Apache HttpClient
5.0. I will get back to you within a few days and will investigate with both,
Tomcat and HttpClient devs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452

Bernhard Friedreich  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #19 from Bernhard Friedreich  ---
Looks like this bug can be closed.

The problems seems to occur from a behavior change in 2.4.43 which is
problematic for the CA SSO WebAgent module.
As soon as I enable the mod_sm module modproxy.tmp files are created (and never
deleted). With the module disabled those files are never even created. Tried it
using a fedora iso image for something really big => no modproxy.tmp file.

Thanks for your help and sorry for wasting your time..

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452

--- Comment #18 from Bernhard Friedreich  ---
Thats how our httpd is compiled:

./configure \
  --prefix=/opt \
  --enable-so \
  --disable-userdir \
  --enable-cache=shared \
  --enable-cgi=shared \
  --enable-expires=shared \
  --enable-headers=shared \
  --enable-logio=shared \
  --enable-mem-cache=shared \
  --enable-mime-magic=shared \
  --enable-nonportable-atomics=yes \
  --enable-proxy=shared \
  --enable-proxy-http=shared \
  --enable-rewrite=shared \
  --enable-ssl=shared \
  --enable-unique-id=shared \
  --enable-usertrack=shared \
  --enable-vhost-alias=shared \
  --enable-mpms-shared='event worker' \
  --with-included-apr \
  --with-included-apr-util \
  --with-ssl=/opt/openssl-1.1.1f

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61179

Donatas Abraitis  changed:

   What|Removed |Added

  Attachment #37264|0   |1
is obsolete||

--- Comment #6 from Donatas Abraitis  ---
Created attachment 37265
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37265=edit
TTLimit.patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452

--- Comment #17 from Bernhard Friedreich  ---
I've just reconfirmed in my local vm that the modproxy.tmp files are cleaned up
using httpd 2.4.41 but not with 2.4.43.

Only differences:
httpd: 2.4.41
mod_jk: 1.2.46

vs

httpd: 2.4.43
mod_jk: 1.2.48

Common:
APR: 1.7.0
APR-UTIL: 1.6.1

As the problem happens using ProxyPass on http and has nothing to do with
mod_jk this has to be some bug in the new 2.4.43 version..

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61179

--- Comment #5 from Donatas Abraitis  ---
Thanks, Nick. Added a patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61179

Donatas Abraitis  changed:

   What|Removed |Added

  Attachment #35048|0   |1
is obsolete||

--- Comment #4 from Donatas Abraitis  ---
Created attachment 37264
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37264=edit
TTLimit.patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61179

--- Comment #3 from Nick Kew  ---
Attached patch would be completed by a patch to document the new directive. 
Somewhere in docs/manual/mod/mpm_common.xml

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452

--- Comment #16 from Bernhard Friedreich  ---
I've also tried via strace using those arguments:

strace -o /root/process_dump -ff /path/to/apache/bin/httpd -f
/path/to/apache/conf/httpd.conf -X

The only unlinks I could find where those:
[root@devbox1 ~]# grep -Hrn "unlink" process_dump*
process_dump.12069:5441:unlink("/path/to/apachelogs/jk-runtime-status.12069.lock")
= 0
process_dump.12069:5442:unlink("/path/to/apachelogs/jk-runtime-status.12069") =
0
process_dump.12135:156:unlink("/tmp/apr-tmp.gYvqb8")   = 0

This is the mode using which modproxy.tmp File was opened
open("/tmp/modproxy.tmp.My4PnF", O_RDWR|O_CREAT|O_EXCL, 0600) = 23

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org



[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452

--- Comment #15 from Bernhard Friedreich  ---
I can now reproduce the problem in my local vm with a more or less stock
centos7 and our self compiled apache.

Running gdb the interesting thing is that file_cleanup is reached for apr-tmp
but never for modproxy.tmp. Sadly there seems to be a mismatch in line numbers
to source - even if the same versions (apr 1.7.0 and apr-util 1.6.1) are used..

Breakpoint 1, ap_proxy_http_prefetch (url=, uri=0x7fffbc010d18,
req=) at mod_proxy_http.c:807
807 rv = spool_reqbody_cl(req, );
(gdb)
Continuing.

Breakpoint 2, apr_file_mktemp (fp=fp@entry=0x7fffe4a63958,
template=0x7fffbc00ed80 "/tmp/apr-tmp.XX", flags=flags@entry=0,
p=p@entry=0x7fffbc009f18) at file_io/unix/mktemp.c:177
177 {
(gdb) c
Continuing.

Breakpoint 3, apr_unix_file_cleanup (thefile=0x7fffbc00ed98) at
file_io/unix/open.c:80
80  rv = file_cleanup(file, 0);
(gdb) c
Continuing.

Breakpoint 2, apr_file_mktemp (fp=fp@entry=0x7fffe4a63b30,
template=0x7fffbc00ee50 "/tmp/modproxy.tmp.XX", flags=flags@entry=0,
p=p@entry=0x7fffbc009f18) at file_io/unix/mktemp.c:177
177 {
(gdb) c
Continuing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org