Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Apache httpd 2.4.40-vote available, did not pass |
|
Author |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3092 Location: Hilversum, NL, EU
|
Posted: Sat 03 Aug '19 12:47 Post subject: Apache httpd 2.4.40-vote available, did not pass |
|
|
Apache httpd 2.4.40 is around the corner, voting at ASF has started.. Expected that this is becoming the final.
ASF and Apachelounge changes :
https://www.apachelounge.com/Changelog-2.4.html
Did not pass the vote, see below.
There is also New C++ Redistributable 14.22.27821.0 (was 14.21.27702.2)
Please give it a try and report here. |
|
Back to top |
|
Jan-E
Joined: 09 Mar 2012 Posts: 1266 Location: Amsterdam, NL, EU
|
Posted: Sun 04 Aug '19 1:28 Post subject: |
|
|
Did anyone test mod_md and got it working?
My working 2.4.39 config fails with 2.4.40. |
|
Back to top |
|
Jan-E
Joined: 09 Mar 2012 Posts: 1266 Location: Amsterdam, NL, EU
|
Posted: Sun 04 Aug '19 13:15 Post subject: Re: Apache httpd 2.4.40-vote available |
|
|
Steffen wrote: | Apache httpd 2.4.40 is around the corner, voting at ASF has started.. Expected that this is becoming the final. |
I do not think so. ASF would be irresponsible to release a version when mod_md is broken. Part of the output of
Code: | devenv Apache_vc16.sln /Build "Release|x64" /Project mod_md |
Quote: | 7>Generating Code...
7>Compiling...
7>md_util.c
7>mod_md.c
7>modules\md\mod_md.c(386,67): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
7>modules\md\mod_md.c(391,67): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
7>modules\md\mod_md.c(601,65): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
7>modules\md\mod_md.c(608,65): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
7>modules\md\mod_md.c(659,57): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
7>modules\md\mod_md.c(702,59): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
7>mod_md_config.c
7>mod_md_drive.c
7>mod_md_os.c
7>mod_md_status.c
7>Generating Code...
7>modules\md\mod_md.c(912,52): warning C4003: not enough arguments for function-like macro invocation 'APLOGNO'
|
These warnings should be fixed before a release. And mod_md.so should be confirmed working. |
|
Back to top |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3092 Location: Hilversum, NL, EU
|
Posted: Sun 04 Aug '19 14:34 Post subject: |
|
|
The APLOGNO warnings warnings are not a reason not to release.
We have more now: mod_proxy mod_http2 mod_ssl mod_md
I am not able to test full the configuration utility mod_md, because it is not supporting my config (SSL only, SNI and no vhosts). |
|
Back to top |
|
Jan-E
Joined: 09 Mar 2012 Posts: 1266 Location: Amsterdam, NL, EU
|
Posted: Sun 04 Aug '19 15:31 Post subject: |
|
|
Steffen wrote: | The APLOGNO warnings are not a reason not to release. |
Well, maybe the warnings are unrelated to the fact that mod_md is broken. See
https://brussel.albatros-amsterdam.nl/managed-domain.png
This is on an (old) copy of the site of my volleyball club, on a devserver that previously was located in Brussels.
With 2.4.39 I removed the md directory, started the server, checked that things were added in the md/staging directory and restarted the server.
Then I replaced 2.4.39 with 2.4.40. I removed the md directory once again (after saving a copy) and tried to start the server. No go. The necessary directoris were created, but nothing was added to the md/staging directory:
Code: | Directory of md.bad
04/08/19 15:23 <DIR> .
04/08/19 15:23 <DIR> ..
04/08/19 15:13 <DIR> accounts
04/08/19 15:13 <DIR> challenges
04/08/19 15:13 <DIR> domains
04/08/19 15:13 116 md_store.json
04/08/19 15:13 <DIR> staging
2 File(s) 116 bytes
Directory of md.bad\accounts
04/08/19 15:13 <DIR> .
04/08/19 15:13 <DIR> ..
0 File(s) 0 bytes
Directory of md.bad\challenges
04/08/19 15:13 <DIR> .
04/08/19 15:13 <DIR> ..
0 File(s) 0 bytes
Directory of md.bad\domains
04/08/19 15:13 <DIR> .
04/08/19 15:13 <DIR> ..
04/08/19 15:13 <DIR> brussel.albatros-amsterdam.nl
0 File(s) 0 bytes
Directory of md.bad\domains\brussel.albatros-amsterdam.nl
04/08/19 15:13 <DIR> .
04/08/19 15:13 <DIR> ..
04/08/19 15:13 514 md.json
1 File(s) 514 bytes
Directory of md.bad\staging
04/08/19 15:13 <DIR> .
04/08/19 15:13 <DIR> ..
0 File(s) 0 bytes
|
The domain does show up as managed domain in server-status. See the screenshot in the link above.
Last edited by Jan-E on Sun 04 Aug '19 21:55; edited 1 time in total |
|
Back to top |
|
Jan-E
Joined: 09 Mar 2012 Posts: 1266 Location: Amsterdam, NL, EU
|
Posted: Sun 04 Aug '19 20:32 Post subject: |
|
|
Steffen wrote: | The APLOGNO warnings are not a reason not to release. |
I checked that. httpd 2.4.39 did not have the APLOGNO warnings in mod_md:
Code: | md_acme.c
md_acme_acct.c
md_acme_authz.c
md_acme_drive.c
md_core.c
md_crypt.c
md_curl.c
md_http.c
md_json.c
md_jws.c
md_log.c
md_reg.c
md_store.c
md_store_fs.c
md_util.c
mod_md.c
mod_md_config.c
mod_md_os.c
Generating Code...
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppBuild.targets(1216,5): warning MSB8012: TargetPath(N:\httpd\modules\md\x64\Release\mod_md.dll) does not match the Linker's OutputFile property value (N:\httpd\modules\md\Release\mod_md.so). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppBuild.targets(1217,5): warning MSB8012: TargetExt(.dll) does not match the Linker's OutputFile property value (.so). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
Creating library .\Release/mod_md.lib and object .\Release/mod_md.exp
LINK : warning LNK4281: undesirable base address 0x70D50000 for x64 image; set base address above 4GB for best ASLR optimization
LINK : warning LNK4013: image size 0xED000 exceeds specified maximum 0x30000
mod_md.vcxproj -> N:\httpd\modules\md\x64\Release\mod_md.dll
Embed .manifest
|
|
|
Back to top |
|
Jan-E
Joined: 09 Mar 2012 Posts: 1266 Location: Amsterdam, NL, EU
|
Posted: Sun 04 Aug '19 21:18 Post subject: |
|
|
And mod_ssl in 2.4.39 had a lot of 'possible loss of data' and 'signed/unsigned mismatch' warnings, but no APLOGNO. In none of the *.log files of httpd 2.4.39 there is a APLOGNO warning. |
|
Back to top |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3092 Location: Hilversum, NL, EU
|
Posted: Tue 06 Aug '19 6:42 Post subject: |
|
|
Vote did not pass.
A minor regression has been detected in mod_md (thanks Jan). |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7371 Location: Germany, Next to Hamburg
|
Posted: Tue 06 Aug '19 9:16 Post subject: |
|
|
Does .40 make it or will there be a .41 soon'ish? |
|
Back to top |
|
Steffen Moderator
Joined: 15 Oct 2005 Posts: 3092 Location: Hilversum, NL, EU
|
Posted: Tue 06 Aug '19 9:28 Post subject: |
|
|
There will be a 41. |
|
Back to top |
|
|
|
|
|
|