Hi there,
I tried to check, whether the few remaining sporadic test failures
during pytest can be solved by updating pebble form 2.4.0 to 2.5.1
(which seems to be the same as 2.5.0).
Unfortunately I get a lot of FAILED md tests with that version. Does
anyone see the same?
Here's some more
Am 07.04.24 um 09:42 schrieb jean-frederic clere:
On 4/6/24 20:02, Rainer Jung wrote:
Hi Jean-Frederic and all,
you didn't write at what point in time you take the thread dump. I see
the SIGTERM messages logged during test execution always during the
last test in each group (http2, md
Hi Jean-Frederic and all,
you didn't write at what point in time you take the thread dump. I see
the SIGTERM messages logged during test execution always during the last
test in each group (http2, md, ...) just because that is the time the
logs are checked by teardown for error messages. At
Hi Stefan and all,
I have these additional RST in some more test cases (it seems the more
runs I do, the more popup). Would it make sense to allow RST after EOF
in *all* tests that look for EOF in
modules/http2/test_800_websockets.py? WDYT?
Thanks and regards,
Rainer
Am 05.04.24 um 09:04
I think I fixed all test failures, hopefully in the correct way. More
eyes welcome.
I have a few additional sporadic ERRORS:
A] ERROR during teardown check for log file errors or warnings (twice):
04.04.2024 21:14:42.205465 ___ ERROR at teardown of
TestStatus.test_md_920_020
Hi there,
first although I saw very few pytest failures, I think the results are
overall fine and good enough for release.
I first had to find out, that I need to build the h2ws websocket client
during httpd build (for websocket tests) and use the right multipart
python module
Thanks!
Am 03.04.24 um 21:13 schrieb Eric Covener:
On Wed, Apr 3, 2024 at 3:03 PM Eric Covener wrote:
On Wed, Apr 3, 2024 at 2:54 PM Rainer Jung wrote:
Minor nit: the format of the SHA hash files has changes. Example:
2.4.58
Minor nit: the format of the SHA hash files has changes. Example:
2.4.58:
fa16d72a078210a54c47dd5bef2f8b9b8a01d94909a51453956b3ec6442ea4c5
*httpd-2.4.58.tar.bz2
2.4.59:
SHA2-256(httpd-2.4.59-rc1.tar.bz2)=
ec51501ec480284ff52f637258135d333230a7d229c3afa6f6c2f9040e321323
I need to see how
Am 03.04.24 um 09:52 schrieb Joe Orton:
On Tue, Apr 02, 2024 at 08:46:46PM -0400, Eric Covener wrote:
This could be due to none of these happening:
- mod_mime didn't send a charset from backend
- no BOM
- no xml2EncDefault (8859-1 effectively by default) on frontend
To make the conf match the
Hi there,
in preparation of the relase I am running the test framework against
recent httpd 2.4.x head.
I am seeing test failures in t/apache/pr64339.t:
# testing : content-type header test for /doc.xml
# expected: 'application/xml; charset=utf-8'
# received: 'application/xml;charset=utf-8'
Hi there,
in the light of the recent xz attack I was wondering, whether we should
also reduce our library dependencies by no longer using sd_notify() in
mod_systemd (thus loading libsystemd and all of its dependencies), but
instead taking the approach to hard code sd_notify functionality.
I
I guess it could be like this: when Mladen originally implemented the by
requests load balancing method in mod_jk he used the count and subtract
method for the counters. He then ported this to mod_proxy_balancer and I
think it is still, how by requests counting woorks there.
There are pros
FYI: here's a list of symbols for which I get deprecation warnings when
compiling httpd 2.4.58 (plus bundled APU) against current OpenSSL 3.1.3.
or 3.0.11:
srclib/apr-util/crypto/apr_crypto_openssl.c:141:5: warning:
'ENGINE_load_builtin_engines' is deprecated (declared at
Am 16.10.23 um 17:08 schrieb Stefan Eissing via dev:
Hi all,
after fixing my merge mistake in rc2 (sorry!), we go again:
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release
://svn.apache.org/viewvc?rev=1913010=rev
Log:
Merge r1912015 from trunk:
mod_ssl: Silence info log message "SSL Library Error: error:0A000126:
SSL routines::unexpected eof while reading" when using
OpenSSL 3 by setting SSL_OP_IGNORE_UNEXPECTED_EOF if
available. [R
Am 14.09.23 um 07:44 schrieb Stefan Eissing via dev:
Am 13.09.2023 um 22:14 schrieb Rainer Jung :
Hi all,
when running the current pytest, I see a gap between two specific test outputs
of more than three minutes:
...
13.09.2023 21:47:46.220943
modules/http2/test_712_buffering.py
Hi all,
when running the current pytest, I see a gap between two specific test
outputs of more than three minutes:
...
13.09.2023 21:47:46.220943
modules/http2/test_712_buffering.py::TestBuffering::test_h2_712_03
PASSED [ 39%]
13.09.2023 21:50:55.456457
Am 07.09.23 um 14:58 schrieb Joe Orton:
On Wed, Aug 30, 2023 at 01:21:11PM +0200, Rainer Jung wrote:
Hi there,
OpenSSL 3 flags some abortive shutdowns as an error different to what 1.1.1
did. This results in info log output in httpd:
[Tue Aug 29 12:33:06.787210 2023] [ssl:info] [pid 1994673
Hi there,
mod_jk for example uses such aging, but only for the non busyness case.
busyness is meant to show the number of currently in-flight requests, so
aging isn't a good fit there. Old load numbers are never part of
busyness. But busyness is the mode that is most sensitive to the numer
Hi JFC,
I have not checked ur current code, but the topic reminds me of our
history in mod_jk land. There we switched the counters to atomics were
available. The other problematic part could be how to handle process
local counters versus global counters.
Busyness was especially problematic
Am 30.08.23 um 13:50 schrieb Stefan Eissing via dev:
Am 30.08.2023 um 13:21 schrieb Rainer Jung :
Hi there,
OpenSSL 3 flags some abortive shutdowns as an error different to what 1.1.1
did. This results in info log output in httpd:
[Tue Aug 29 12:33:06.787210 2023] [ssl:info] [pid 1994673
Hi there,
OpenSSL 3 flags some abortive shutdowns as an error different to what
1.1.1 did. This results in info log output in httpd:
[Tue Aug 29 12:33:06.787210 2023] [ssl:info] [pid 1994673:tid 1994737]
SSL Library Error: error:0A000126:SSL routines::unexpected eof while reading
[Tue Aug 29
Oups and thanks!
Am 04.05.23 um 12:30 schrieb yla...@apache.org:
Author: ylavic
Date: Thu May 4 10:30:25 2023
New Revision: 1909606
URL: http://svn.apache.org/viewvc?rev=1909606=rev
Log:
Follow up to r1909429: Fix scope/block syntax.
Modified:
Am 04.05.23 um 10:34 schrieb Ruediger Pluem:
This is a formal vote on whether we should move our read/write repository from
Subversion to Git.
This means that our latest read/write repository will be no longer available
via svn.apache.org. It
will be available via Git at
Am 09.03.23 um 11:29 schrieb Stefan Eissing via dev:
Am 09.03.2023 um 11:22 schrieb Rainer Jung :
Puzzle partially solved: once I add "--header 'content-type:
application/x-www-form-urlencoded'" to the nghttp call, the problem seems fixed -
with and without deflate. No more han
p, so I am still not sure, whether the odd behavior without
the header is a bug.
Am 09.03.23 um 11:03 schrieb Rainer Jung:
OK, I can test in a standalone situation now.
The problem goes away, once I use curl, even with h2.
The problem also goes away, once I disable deflate compression for the
OK, I can test in a standalone situation now.
The problem goes away, once I use curl, even with h2.
The problem also goes away, once I disable deflate compression for the
response. But curl and nghttp behave different: nghttp hangs after
receiving the response body (no deflate), curl normally
.
Thanks and regards,
Rainer
Am 09.03.23 um 09:19 schrieb Ruediger Pluem:
On 3/8/23 10:44 PM, Rainer Jung wrote:
Hi there,
I currently get three consistent pytest failures:
Do A) and B) work if you do the requests via HTTP/1.1?
Regards
Rüdiger
Thanks for the tip. I already did the "run only one test case" and I
fixed the LogLevel in test.conf to include trace8. So I guess there will
not be any additional CGI logging available. But good to know the "-vvv".
Thanks and regards,
Rainer
Am 09.03.23 um 09:33 schrieb Stefan Eissing via
Hi there,
I currently get three consistent pytest failures:
A) FAILED modules/http2/test_202_trailer.py::TestTrailers::test_h2_202_03b
Response code is 500 and trace 8 server log shows:
- we see the right request
[Wed Mar 08 22:03:35.699234 2023] [aptest:info] [pid 4606:tid
Not a showstopper, but: srclib/apr/configure was again generated with
autoconf 2.70+ (2.71). This triggers a bug which is fixed in APR 1.7.x
head, but the fix has not been released as there was not APR release vor
almost 4 years now.
Since the bundled APR/APU are not actually part of the
Hi there,
I looked at our escaping functions for logs due to the need of doing
JSON logging. In principle one can output JSON by using appropriate log
format definitions in the httpd config. Most special characters in JSON
are already properly escaped in our output.
But there is one
Hi Stefan,
the PR is:
https://bz.apache.org/bugzilla/show_bug.cgi?id=66282
Let me know, in case you can not reproduce it, or I should test something!
Best regards,
Rainer
Hi all,
today I stumbled into an unexpected request denial by a rule in the
mod_security Core Rule Set 3. It denies requests without body, that have
Transfer-Encoding chunked set.
When I send a normal GET request, without body, no Transfer-Encoding and
no Content-Length, to httpd and proxy
Hi there,
I ran the pytest suite on SLES 12+15 and RHEL 7+8 for 2.4.54 plus
OpenSSL 1.1.1p. Ran it for event, worker and prefork and with OpenSSL
1.1.1 and 3.0 in the client.
I observe sporadic segmentation faults on all of those platforms and for
all MPMs and all OpenSSL versions in the
Am 21.06.2022 um 07:38 schrieb Ruediger Pluem:
On 6/20/22 10:54 PM, rj...@apache.org wrote:
Author: rjung
Date: Mon Jun 20 20:54:14 2022
New Revision: 1902117
URL: http://svn.apache.org/viewvc?rev=1902117=rev
Log:
*) mod_heartmonitor: Allow "HeartbeatMaxServers 0"
to use file based
I wonder, what the following test is expected to test? I can't really
make it work reliably here. Sometimes I get an ENOMEM on the server,
sometimes it takes a long time and much CPU, sometimes the client gets a
596 AnyEvent::HTTP error and sometimes it runs ok.
Am 01.06.2022 um 15:03 schrieb
Am 06.06.2022 um 16:25 schrieb Stefan Eissing:
Here we go again! Sorry for the repeats, but that is why we build candidates,
right?
Hi all,
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the
Am 25.05.2022 um 14:15 schrieb Stefan Eissing:
Anyone feeling release vibes in the air?
it's been a good 2.5 months and some things have accumulated.
Maybe the start of June would be a good target?
+1 and thanks!
Rainer
Hi Jim,
it looks like the unrelated file
changes-entries/mod_proxy_log_backend_port.txt was removed by accident
during this commit? I don't see its contents already in CHANGES.
I had not yet used the make target "update-changes" when applying the
backend port patch, so the changes-entries
)
Result: FAIL
Failed 1/141 test programs. 1/7232 subtests failed.
...
Am 17.05.2022 um 15:24 schrieb Rainer Jung:
Not yet a full explanation but:
- the build fails due to "The job exceeded the maximum log length, and
has been terminated." shortly before line 30.000
- the
Not yet a full explanation but:
- the build fails due to "The job exceeded the maximum log length, and
has been terminated." shortly before line 30.000
- the difference to the succeeeding "Linux Ubuntu Focal, ASan" is, that
the ErrorLog of the run is not part of this log output handled by
Am 10.05.2022 um 16:23 schrieb Eric Covener:
I was looking at making some tests run more quietly, but mod_dumpio
uses ap_log_cerror even though it always has a ap_filter_t when it's
doing its real work.
While this would still leave some early logging (pre-location walk)
w/o the per-dir loglevel
them there. Could you
give this a shot?
Kind Regards,
Stefan
Am 24.04.2022 um 22:03 schrieb Rainer Jung :
Hi all,
at the end of the test runs in the pytest suite, TestBuffering.test_h2_712_03
checks for warnings or errors logged in the httpd error log. None are allowed,
but test
Hi all,
at the end of the test runs in the pytest suite,
TestBuffering.test_h2_712_03 checks for warnings or errors logged in the
httpd error log. None are allowed, but test
test_101_ssl_reneg.py
[ssl:error] [pid 15298:tid 140040420189952] SSL Library Error:
error:0AC1:SSL routines::no
geschreven:
Am 07.04.2022 um 13:04 schrieb Rainer Jung :
Hi there,
during my experiments with the nice pytest based test suite against 2.4.x I noticed, that
many mod_md tests need "a2md". The sources for this commandline tool ar in
Stefan's GitHub repos for mod_md, but not inside the
Hi there,
during my experiments with the nice pytest based test suite against
2.4.x I noticed, that many mod_md tests need "a2md". The sources for
this commandline tool ar in Stefan's GitHub repos for mod_md, but not
inside the httpd 2.4.x source tree.
I have not really checked, what a2md
Thaks, will switch to that one. Should have reembered it ...
Am 05.04.2022 um 14:04 schrieb Stefan Eissing:
Am 05.04.2022 um 14:01 schrieb Rainer Jung :
Hi Stefan,
Am 05.04.2022 um 13:49 schrieb Stefan Eissing:
Which test suite, the one in trunk or the one from github? Both work best
.x release (candidate)?
Thanks and regards,
Rainer
Am 05.04.2022 um 13:47 schrieb Rainer Jung :
I try to make the mod_h2 test suite run for me. Some difficulties are expected
due to my non-standard setup, but the first test that seems to fail in a way I
am not directly blaming myself is
fuzz
I try to make the mod_h2 test suite run for me. Some difficulties are
expected due to my non-standard setup, but the first test that seems to
fail in a way I am not directly blaming myself is
fuzz header
* on http://test.example.org:12345: super-long...--- gen/expect_431
2022-04-05
Am 28.03.2022 um 15:24 schrieb Stefan Eissing:
Am 28.03.2022 um 14:28 schrieb Rainer Jung :
I am thinking about adding a JSON output format to mod_status and mod_info as
an option controlled by a query string parameter.
Since writing simple data structures from these modules is much
I am thinking about adding a JSON output format to mod_status and
mod_info as an option controlled by a query string parameter.
Since writing simple data structures from these modules is much simpler
than parsing and processing a JSON structure, I would expect it to be
based on simple
First thanks to Stefan for downgrading his release system. It is a good
workaround for the observed problems.
Since downgrades are not a long term solution, here's the status info to
avoid confusion.
We observed two problems that had to do with using a recent autoconf
version (2.70 an
Am 09.03.2022 um 13:58 schrieb Ruediger Pluem:
On 3/9/22 11:34 AM, Rainer Jung wrote:
Am 09.03.2022 um 08:37 schrieb Ruediger Pluem:
On 3/8/22 10:09 PM, Rainer Jung wrote:
You gcc 4.8 workaround for _Thread_local still looks good.
Solaris builds and all unit tests not yet done
Am 09.03.2022 um 08:37 schrieb Ruediger Pluem:
On 3/8/22 10:09 PM, Rainer Jung wrote:
You gcc 4.8 workaround for _Thread_local still looks good.
Solaris builds and all unit tests not yet done but compiles fine for all my
Linuxes.
Thanks!
Thanks for testing. I committed to trunk
Am 08.03.2022 um 18:22 schrieb Rainer Jung:
Am 08.03.2022 um 17:06 schrieb Ruediger Pluem:
On 3/8/22 4:38 PM, Rainer Jung wrote:
Am 08.03.2022 um 16:33 schrieb Rainer Jung:
Am 07.03.2022 um 16:55 schrieb Stefan Eissing:
Hi all,
Please find below the proposed release tarball
Am 08.03.2022 um 17:06 schrieb Ruediger Pluem:
On 3/8/22 4:38 PM, Rainer Jung wrote:
Am 08.03.2022 um 16:33 schrieb Rainer Jung:
Am 07.03.2022 um 16:55 schrieb Stefan Eissing:
Hi all,
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev
Am 08.03.2022 um 16:33 schrieb Rainer Jung:
Am 07.03.2022 um 16:55 schrieb Stefan Eissing:
Hi all,
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release
this candidate
Am 07.03.2022 um 16:55 schrieb Stefan Eissing:
Hi all,
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release
this candidate tarball httpd-2.4.53-rc1 as 2.4.53:
[ ] +1: It's
Small typo below ...
Am 08.02.2022 um 12:04 schrieb yla...@apache.org:
Author: ylavic
Date: Tue Feb 8 11:04:49 2022
New Revision: 1897858
URL: http://svn.apache.org/viewvc?rev=1897858=rev
Log:
Sync CHANGES entries. [skip ci]
Removed:
Aaah, sorry, it did come in now,, son't know whether via dev@ or
announce@. Thanks.
Am 20.12.2021 um 10:53 schrieb Stefan Eissing:
The mailings to announce lists continue to bother me. The release announcement
is the the moderation queue (hopefully) and the cveprocess mails go right
through
Hmmm, still no announcement mail received, or did I miss it?
Am 20.12.2021 um 10:53 schrieb Stefan Eissing:
The mailings to announce lists continue to bother me. The release announcement
is the the moderation queue (hopefully) and the cveprocess mails go right
through to the list. This is not
Am 16.12.2021 um 15:03 schrieb Stefan Eissing:
Hi all,
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release
this candidate tarball httpd-2.4.52-rc1 as 2.4.52:
[X] +1: It's
Am 17.12.2021 um 16:45 schrieb Stefan Eissing:
Am 17.12.2021 um 16:22 schrieb Rainer Jung :
At least on Linux (SLES 11/12/15, RHEL 6/7/8) I run into a configure error for
APR from the deps tarball due to that configure being created with autoconf
2.70 instead of 2.69 used for 2.4.51
At least on Linux (SLES 11/12/15, RHEL 6/7/8) I run into a configure
error for APR from the deps tarball due to that configure being created
with autoconf 2.70 instead of 2.69 used for 2.4.51:
configure: error: could not determine the string function for int64_t
It comes from defining some
Thanks for the cool team effort and your work as RM!
I lost track about the correct expectation but wanted to note, that
https://dist.apache.org/repos/dist/dev/httpd/
does not contain a KEYS file. IMHO it did for the previous two releases,
but maybe the requirements changed.
Thanks!
Rainer
Am 07.10.2021 um 14:27 schrieb yla...@apache.org:
Modified: httpd/httpd/branches/2.4.x/include/ap_mmn.h
URL:
http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/include/ap_mmn.h?rev=1893977=1893976=1893977=diff
==
Thanks for testing Dennis. We need to get this release out quick due to
regressions, so it wasn't the right moment to apply the OpenSSL patch.
I'm confident, that Joe's OpenSSL 3.0.0 patch will be included in the
next regular 2.4 release.
Best regards,
Rainer
Am 02.10.2021 um 13:01 schrieb
Am 16.09.2021 um 13:59 schrieb ste...@eissing.org:
Am 16.09.2021 um 13:57 schrieb ste...@eissing.org:
Am 16.09.2021 um 13:50 schrieb ste...@eissing.org:
Am 16.09.2021 um 13:46 schrieb Daniel Gruno :
it's on announce@httpd.a.o already. I modded it through.
You need to send it to
Hi Dennis,
Am 13.09.2021 um 11:05 schrieb Dennis Clarke:
On 9/13/21 04:22, Joe Orton wrote:
On Mon, Sep 13, 2021 at 01:23:37AM -0400, Dennis Clarke wrote:
ALL :
I may receive no reply to this but in general I have been able to build
Apache httpd from any release tarball as well as from
Hi there,
any chance we find an RM for a APR 1.7.1 release? At least there was the
fix for CVE-2021-35940 and CHANGES contains 15 more items (many of them
platform specific or build improvements). Last release 1.7.0 was in
April 2019.
For APR-util I don't know the current state and release
Thanks for the headroom explanation Yann, good reading!
Rainer
Am 25.08.2021 um 13:23 schrieb Yann Ylavic:
On Tue, Jun 29, 2021 at 3:00 PM Rainer Jung wrote:
Am 29.06.2021 um 14:31 schrieb Stefan Eissing:
Can comment really on the diff, but totally agree on the goal to minimize
Am 29.06.2021 um 14:31 schrieb Stefan Eissing:
Can comment really on the diff, but totally agree on the goal to minimize the
unresponsive time and make graceful less disruptive.
So +1 for that.
+1 on the intention as well.
Not sure, whether that means people would need more headroom in the
Hi there,
is my understanding correct, that even httpd trunk (and then also 2.4.x)
needs LDAP support in APR/APU to build mod_ldap and mod_authnz_ldap?
So since we removed LDAP support from APR trunk, that means those
modules currently can not be build using APR trunk, neither in httpd
FYI: the problems I observed when running the httpd test suite using an
OpenSSL 0.9.8zh based client against a server build using OpenSSL 3.0.0
originated in the fact, that OpenSSL 3.0.0 by default no longer allows
RSA SHA1 and DSA SHA1 as signature algorithms. But 0.9.8 only support
TLS 1.0
Am 17.05.2021 um 23:36 schrieb Christophe JAILLET:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.48:
[X] +1: It's not just
Am 20.05.2021 um 14:07 schrieb Noel Butler:
On 20/05/2021 21:19, Rainer Jung wrote:
Hi there,
I saw the following build warnings in 2.4.48:
modules/md/md_crypt.c:1382: warning: passing argument 1 of
‘BIO_new_mem_buf’ discards qualifiers from pointer target type
[-Wdiscarded-qualifiers
Hi there,
I saw the following build warnings in 2.4.48:
modules/md/md_crypt.c:1382: warning: passing argument 1 of
‘BIO_new_mem_buf’ discards qualifiers from pointer target type
[-Wdiscarded-qualifiers]
=> happens only when building against OpenSSL 1.0.2 (initial release, no
letter suffix).
Am 22.04.2021 um 11:25 schrieb Christophe JAILLET:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.47:
[ ] +1: It's not just
OK, it is a bug or behavior change in the "openssl crl" command line for
3.0.0 that leads to the CRL symlinks not being created any more.
I raised
https://github.com/openssl/openssl/issues/15031
Regards,
Rainer
Am 26.04.2021 um 15:34 schrieb Rainer Jung:
I am still investigati
I am still investigating further, bit this is due to the fact, that the
CRL symlink in the crl directory is missing. Might be a local
integration issue. Will look further.
Am 26.04.2021 um 13:27 schrieb Rainer Jung:
When building 2.4.47 using OpenSSL 3.0.0alpha15 and running the test
suite
When building 2.4.47 using OpenSSL 3.0.0alpha15 and running the test
suite, the proxy TLS connection fails with "Certificate Verification:
Error (3): unable to get certificate CRL":
[Mon Apr 26 10:00:50.352111 2021] [ssl:trace3] [pid 16699:tid
140438686086912] ssl_engine_kernel.c(2213):
FYI: here's a list of symbols for which I get deprecation warnings when
compiling httpd 2.4.47 (plus bundled APU) against current OpenSSL
3.0.0alpha15:
srclib/apr-util/crypto/apr_crypto_openssl.c:141:5
ENGINE_load_builtin_engines
srclib/apr-util/crypto/apr_crypto_openssl.c:142:5
:
Am 10.08.2020 um 16:38 schrieb Rainer Jung :
Hi there,
the .gitignore file in modules/http2 contains "Makefile.in". That's probably OK
for the upstream Github variant, which contains a Makefile.am, but in our svn repos for
httpd the Makefile.in is needed as the source of the Makefile
Hi there,
the .gitignore file in modules/http2 contains "Makefile.in". That's
probably OK for the upstream Github variant, which contains a
Makefile.am, but in our svn repos for httpd the Makefile.in is needed as
the source of the Makefile generation.
Of course our svn doesn't care about
and to ensure the type of release (bug, security, enhancement)
is correct. It appears as though the file was just changed, but really
it's just because the text was bumped as-is from the 'dev' location to
the 'dist' location.
--
Daniel Ruggeri
On August 5, 2020 7:23:33 AM CDT, Rainer Jung
wrote
no longer linked against -lsystemd if mod_systemd
+ is enabled (and built as a DSO). [Rainer Jung]
+
+ *) mod_proxy_http2: respect ProxyTimeout settings on backend connections
+ while waiting on incoming data. [Ruediger Pluem, Stefan Eissing]
+
Changes with Apache 2.4.43
+ *) mod_ssl: F
ith a auto-loaded
openssl.cnf which contained the lines to load the legacy provider. The
provider got loaded, but still the handshakes with the old OpenSSL fail.
Don't know why. Probably not the biggest problem, because 0.9.8 based
clients should really not matter when thinking about 3.0.0 su
Am 01.08.2020 um 16:13 schrieb Daniel Ruggeri:
Hi, all;
Third time is a charm! Please find below the proposed release tarball
and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.46:
[X] +1:
Hi there,
during release testing for 2.4.45 I also built and tested using OpenSSL
3.0.0alpha5 on the server. Overall first results are pretty good:
- a few deprecation warnings during compilation:
modules/ssl/ssl_engine_config.c:610:5: warning: 'ENGINE_by_id' is
deprecated
(who fixed it on trunk) oand/or Christophe, who
backported it.
Best regards,
Rainer
Am 31.07.2020 um 15:36 schrieb Rainer Jung:
Since there wasn't yet any reaction to Daniel's question: Is anybody
right now working on more warnings fixes for Windows?
The most prominent one (missing APLO
Since there wasn't yet any reaction to Daniel's question: Is anybody
right now working on more warnings fixes for Windows?
The most prominent one (missing APLOGNo number = missing macro argument)
IMHO was already fixed by Christophe in r1880438. Anything else worth
waiting for or are we (is
Am 27.04.2020 um 15:57 schrieb Joe Orton:
On Sat, Apr 25, 2020 at 08:10:40PM +0200, Rainer Jung wrote:
Patch available at
home.apache.org/~rjung/patches/httpd-trunk-mon-snaps-v1_2.patch
Very nice! +1 from me.
Does the times_per_thread logic still make any sense? It's always been
wrong
Am 27.04.2020 um 17:28 schrieb Yann Ylavic:
On Mon, Apr 27, 2020 at 5:18 PM Rainer Jung wrote:
Hi Yann,
Am 27.04.2020 um 16:40 schrieb Yann Ylavic:
Hi Rainer,
On Mon, Apr 27, 2020 at 3:17 PM Rainer Jung wrote:
Thanks for this.
Could you please create this as a PR on github as well
Hi Yann,
Am 27.04.2020 um 16:40 schrieb Yann Ylavic:
Hi Rainer,
On Mon, Apr 27, 2020 at 3:17 PM Rainer Jung wrote:
Thanks for this.
Could you please create this as a PR on github as well? This ensures that all
the Travis tests are run for your patch.
Thanks Rüdiger. Done and indeed
Am 27.04.2020 um 08:57 schrieb Ruediger Pluem:
On 4/25/20 8:10 PM, Rainer Jung wrote:
Patch available at
home.apache.org/~rjung/patches/httpd-trunk-mon-snaps-v1_2.patch
Thanks for this.
Could you please create this as a PR on github as well? This ensures that all
the Travis tests are run
ange not yet part of the patch.
It compiles fine (maintainer mode) on RHEL 7 x86_64 and on Solaris 10
Sparc and I did some tests with mod_status and mod_systemd.
Regards,
Rainer
Am 24.04.2020 um 18:32 schrieb Rainer Jung:
Am 24.04.2020 um 16:21 schrieb Joe Orton:
On Fri, Apr 24, 2020 at 12:17
Am 24.04.2020 um 16:21 schrieb Joe Orton:
On Fri, Apr 24, 2020 at 12:17:19PM +0200, Rainer Jung wrote:
Thinking further: I think it would make sense to have a module or core
implement the monitor hook to generate that derived data (requests/sec,
bytes/sec, durationMs/request, avgConcurrency
- mod_status - instead of the long term averages since start. It could
probably be added to the code that already provides "sload". That way
mod_status would also profit from the more precise average values (taken
over the last monitor interval).
Regards,
Rainer
Am 23.04.2020 um 21:29 schr
Hi all,
triggered by the new mod_systemd I drafted a patch to enhance the
monitoring data it provides during the monitor hook run.
Currently it publishes important data, like idle and busy slots and
total request count, but also not so useful info like requests/second
and bytes/second as a
1 - 100 of 1303 matches
Mail list logo
