[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

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

[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

https://bz.apache.org/bugzilla/show_bug.cgi?id=61179 Donatas Abraitis changed: What|Removed |Added Attachment #37265|0 |1 is obsolete|

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

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

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

https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 Bernhard Friedreich changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

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

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 \

[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

https://bz.apache.org/bugzilla/show_bug.cgi?id=61179 Donatas Abraitis changed: What|Removed |Added Attachment #37264|0 |1 is obsolete|

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

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:

[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

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:

[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

https://bz.apache.org/bugzilla/show_bug.cgi?id=61179 Donatas Abraitis changed: What|Removed |Added Attachment #35048|0 |1 is obsolete|

[Bug 61179] TTLimit directive to set maximum allowed IP_TTL

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.

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

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:

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

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