Re: [VOTE] Release 2.3.15-beta as beta
Which post?? The only thing on this thread is something about mod_rewrite and SSL. On Nov 14, 2011, at 4:33 PM, William A. Rowe Jr. wrote: On 11/9/2011 8:24 AM, Jim Jagielski wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... If you did not [announce]... you might want to review Steffan's post first. Looks like a pretty serious all-platform regression between mod_proxy and ap_pregsub.
Re: [VOTE] Release 2.3.15-beta as beta
I found the post... IMO, this should not hold off the release at this point... On Nov 15, 2011, at 11:57 AM, Jim Jagielski wrote: Which post?? The only thing on this thread is something about mod_rewrite and SSL.
Re: [VOTE] Release 2.3.15-beta as beta
On 11/15/2011 11:22 AM, Jim Jagielski wrote: I found the post... IMO, this should not hold off the release at this point... It's beta, they get to keep all the pieces :) But it suggests the ap_pregsub fix is not ready for 2.2-stable, not until this is rooted out.
Re: [VOTE] Release 2.3.15-beta as beta
On 11/9/2011 8:24 AM, Jim Jagielski wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... If you did not [announce]... you might want to review Steffan's post first. Looks like a pretty serious all-platform regression between mod_proxy and ap_pregsub.
Re: [VOTE] Release 2.3.15-beta as beta
On 11/11/2011 13:28, Stefan Fritsch wrote: Are the build problems on Windows a blocker? I think we verbally agreed that they weren't, so unless someone vetoes that statement on-list, we're good to go. Having said that, it's still on my personal to-do list (eventually) Issac
Re: [VOTE] Release 2.3.15-beta as beta
Forgot:
Build with apr-1.4.5 apr-util-1.3.12 apr-iconv-1.2.1 pcre 8.20 lua 5.1
libxml2 2.7.8 openssl-1.0.0e zlib-1.2.5
Stefan, you wrote:
- convince some more people to install it on their production servers
(Steffen?)
I like to do, but the SSL/Rewrite issue below is blocking here to give it a
try.
Steffen
-Original Message-
From: Steffen
Sent: Saturday, November 12, 2011 4:26 PM Newsgroups:
gmane.comp.apache.devel
To: dev@httpd.apache.org
Subject: Re: [VOTE] Release 2.3.15-beta as beta
Building fine on Windows, except mod_lua is complaining that it cannot fine
mod_ssl.h, just copied it and all fine.
Still the issue:
When run in DOS box, not shutting down when closing window, as service no
problem.
A real problematic one is:
When running still issues with SSL, pages and/or image not displayed, is
random. Some errors from the browser:
Unable to make a secure connection to the server. This may be a problem with
the server, or it may be requiring a client authentication certificate that
you don't have.
Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.
The webpage at https://www.land10mail.com/ might be temporarily down or it
may have moved permanently to a new web address.
Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Unknown error
With 2.2.21 and the exact same config, no problems.
The config is:
For SSL, running a Apache 443 only in front of a Apache 80. Using signed
certificate.
It is a minimal config with a commonly used rewrite:
Listen 443
SSLEngine on
DocumentRoot f:/web/unknown
RewriteEngine on
RewriteRule /(.*) http://%{HTTP_HOST}/$1 [P,L]
In the log no clue, only
[ssl:info] [pid 6836:tid 2588] (70014)End of file found: [client
85.223.52.177:38857] SSL input filter read failed.
But that I see also with 2.2.21
Looks like more errors when I have AcceptFilter https none instead of
leaving this out.
Steffen
-Original Message-
From: Jim Jagielski
Sent: Wednesday, November 09, 2011 3:24 PM Newsgroups:
gmane.comp.apache.devel
To: dev@httpd.apache.org
Subject: [VOTE] Release 2.3.15-beta as beta
The 2.3.15-beta (prerelease) tarballs are available for download at test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as 2.3.15-beta BETA and,
with luck, this will be our last beta and the next release in ~2weeks
or less will be 2.4.0 GA!!
Vote will last the normal 72 hours...
[RESULT] Re: [VOTE] Release 2.3.15-beta as beta
The vote is CLOSED and passes with many more than 3 +1 (binding) votes… Thx to all… I will start the move to release during the day with hopes that we can announce tomorrow (Monday)!! w00t! On Nov 9, 2011, at 6:24 AM, Jim Jagielski wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours...
Re: [VOTE] Release 2.3.15-beta as beta
Building fine on Windows, except mod_lua is complaining that it cannot fine
mod_ssl.h, just copied it and all fine.
Still the issue:
When run in DOS box, not shutting down when closing window, as service no
problem.
A real problematic one is:
When running still issues with SSL, pages and/or image not displayed, is
random. Some errors from the browser:
Unable to make a secure connection to the server. This may be a problem with
the server, or it may be requiring a client authentication certificate that
you don't have.
Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.
The webpage at https://www.land10mail.com/ might be temporarily down or it
may have moved permanently to a new web address.
Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Unknown error
With 2.2.21 and the exact same config, no problems.
The config is:
For SSL, running a Apache 443 only in front of a Apache 80. Using signed
certificate.
It is a minimal config with a commonly used rewrite:
Listen 443
SSLEngine on
DocumentRoot f:/web/unknown
RewriteEngine on
RewriteRule /(.*) http://%{HTTP_HOST}/$1 [P,L]
In the log no clue, only
[ssl:info] [pid 6836:tid 2588] (70014)End of file found: [client
85.223.52.177:38857] SSL input filter read failed.
But that I see also with 2.2.21
Looks like more errors when I have AcceptFilter https none instead of
leaving this out.
Steffen
-Original Message-
From: Jim Jagielski
Sent: Wednesday, November 09, 2011 3:24 PM Newsgroups:
gmane.comp.apache.devel
To: dev@httpd.apache.org
Subject: [VOTE] Release 2.3.15-beta as beta
The 2.3.15-beta (prerelease) tarballs are available for download at test:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as 2.3.15-beta BETA and,
with luck, this will be our last beta and the next release in ~2weeks
or less will be 2.4.0 GA!!
Vote will last the normal 72 hours...
Re: [VOTE] Release 2.3.15-beta as beta
+1 for beta on AIX/PPC64/xlc -- httpd.conf had all mods commented but after correcting test suite ran clean after removal of ap_expr recursive test.
Re: [VOTE] Release 2.3.15-beta as beta
On Wed, 9 Nov 2011, Jim Jagielski wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... +1 for beta, tested on Debian stable, test suite passes without error. Are the build problems on Windows a blocker?
Re: [VOTE] Release 2.3.15-beta as beta
On Wed, Nov 9, 2011 at 1:24 PM, Jeff Trawick traw...@gmail.com wrote: On Wed, Nov 9, 2011 at 6:24 AM, Jim Jagielski j...@jagunet.com wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... Is anyone seeing this? Test Summary Report --- t/modules/cgi.t (Wstat: 0 Tests: 53 Failed: 0) Parse errors: Bad plan. You planned 58 tests but ran 53. t/modules/proxy.t (Wstat: 0 Tests: 15 Failed: 2) Failed tests: 9-10 It got worse after enabling the mod_ssl build and retesting, then got significantly better after installing libwww-perl-5.837.tar.gz to use in lieu of Ubuntu/Debian-provided 6.0.2. Here's what's left: t/ssl/v2.t .. /usr/bin/perl: symbol lookup error: /usr/local/lib/perl/5.12.4/auto/Crypt/SSLeay/SSLeay.so: undefined symbol: SSLv2_client_method t/ssl/v2.t .. Dubious, test returned 127 (wstat 32512, 0x7f00) Failed 1/1 subtests Not an httpd problem. +1 for beta release of 2.3.15
Re: [VOTE] Release 2.3.15-beta as beta
Stefan, Which build problem? mod_lua?, I've never seen release blocked on a a alpha/beta nor do I remember screaming and blocking a release by a simple problem with a module, libhttpd is a whole different matter, as that means nothing builds, therefore nothing works. mod_watchdog still crashes the child process when it hits that code, I've never -1 it that I can remember. That reminds me, I need to rehash this with Mladen tho I still stand on my same conclusion, but I can put some reasoning behind it now other than it makes the module crash. Cheers, Gregg On 11/11/2011 1:28 PM, Stefan Fritsch wrote: On Wed, 9 Nov 2011, Jim Jagielski wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... +1 for beta, tested on Debian stable, test suite passes without error. Are the build problems on Windows a blocker?
Re: [VOTE] Release 2.3.15-beta as beta
On 11/9/2011 6:24 AM, Jim Jagielski wrote: I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... +1 for beta
Re: [VOTE] Release 2.3.15-beta as beta
On Fri, 11 Nov 2011, Gregg L. Smith wrote: Stefan, Which build problem? mod_lua?, I've never seen release blocked on a a Yes, I meant the missing include path. alpha/beta nor do I remember screaming and blocking a release by a simple problem with a module, libhttpd is a whole different matter, as that means nothing builds, therefore nothing works. mod_watchdog still crashes the child process when it hits that code, I've never -1 it that I can remember. OK, fine with me.
[VOTE] Release 2.3.15-beta as beta
The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours...
Re: [VOTE] Release 2.3.15-beta as beta
Hi Jim, it looks like your key expired last Friday? % gpg --verify ../incoming/httpd/trunk/2.3.15/httpd-2.3.15-beta.tar.gz.asc gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made November 9, 2011 3:20:26 PM CET using RSA key ID 791485A8 gpg: Good signature from Jim Jagielski (Release Signing Key) j...@apache.org gpg: aka Jim Jagielski j...@jimjag.com gpg: aka Jim Jagielski j...@jagunet.com % gpg --list-keys 791485A8 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/791485A8 2010-11-04 uid Jim Jagielski (Release Signing Key) j...@apache.org uid Jim Jagielski j...@jimjag.com uid Jim Jagielski j...@jagunet.com sub 4096R/9B6D9BF7 2010-11-04 Regards, Rainer On 09.11.2011 06:24, Jim Jagielski wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours...
Re: [VOTE] Release 2.3.15-beta as beta
On 09.11.2011 07:43, Rainer Jung wrote: Hi Jim, it looks like your key expired last Friday? Oups, was so convinced it is new, that I didn't see it already expired a year ago. Maybe you should sign 2.4.0 with a new one? Rainer % gpg --verify ../incoming/httpd/trunk/2.3.15/httpd-2.3.15-beta.tar.gz.asc gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made November 9, 2011 3:20:26 PM CET using RSA key ID 791485A8 gpg: Good signature from Jim Jagielski (Release Signing Key) j...@apache.org gpg: aka Jim Jagielski j...@jimjag.com gpg: aka Jim Jagielski j...@jagunet.com % gpg --list-keys 791485A8 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/791485A8 2010-11-04 uid Jim Jagielski (Release Signing Key) j...@apache.org uid Jim Jagielski j...@jimjag.com uid Jim Jagielski j...@jagunet.com sub 4096R/9B6D9BF7 2010-11-04 Regards, Rainer
Re: [VOTE] Release 2.3.15-beta as beta
2010-11-04 is the day I created the new key… it's unexpired (at least from what I can see ;) ) On Nov 9, 2011, at 7:52 AM, Rainer Jung wrote: On 09.11.2011 07:43, Rainer Jung wrote: Hi Jim, it looks like your key expired last Friday? Oups, was so convinced it is new, that I didn't see it already expired a year ago. Maybe you should sign 2.4.0 with a new one? Rainer % gpg --verify ../incoming/httpd/trunk/2.3.15/httpd-2.3.15-beta.tar.gz.asc gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made November 9, 2011 3:20:26 PM CET using RSA key ID 791485A8 gpg: Good signature from Jim Jagielski (Release Signing Key) j...@apache.org gpg: aka Jim Jagielski j...@jimjag.com gpg: aka Jim Jagielski j...@jagunet.com % gpg --list-keys 791485A8 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/791485A8 2010-11-04 uid Jim Jagielski (Release Signing Key) j...@apache.org uid Jim Jagielski j...@jimjag.com uid Jim Jagielski j...@jagunet.com sub 4096R/9B6D9BF7 2010-11-04 Regards, Rainer
Re: [VOTE] Release 2.3.15-beta as beta
Bring it (the key) tonight :) On 09/11/2011 11:12, Jim Jagielski wrote: 2010-11-04 is the day I created the new key… it's unexpired (at least from what I can see ;) ) On Nov 9, 2011, at 7:52 AM, Rainer Jung wrote: On 09.11.2011 07:43, Rainer Jung wrote: Hi Jim, it looks like your key expired last Friday? Oups, was so convinced it is new, that I didn't see it already expired a year ago. Maybe you should sign 2.4.0 with a new one? Rainer % gpg --verify ../incoming/httpd/trunk/2.3.15/httpd-2.3.15-beta.tar.gz.asc gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made November 9, 2011 3:20:26 PM CET using RSA key ID 791485A8 gpg: Good signature from Jim Jagielski (Release Signing Key) j...@apache.org gpg: aka Jim Jagielski j...@jimjag.com gpg: aka Jim Jagielski j...@jagunet.com % gpg --list-keys 791485A8 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/791485A8 2010-11-04 uid Jim Jagielski (Release Signing Key) j...@apache.org uid Jim Jagielski j...@jimjag.com uid Jim Jagielski j...@jagunet.com sub 4096R/9B6D9BF7 2010-11-04 Regards, Rainer
Re: [VOTE] Release 2.3.15-beta as beta
Already sent to ST yesterday… On Nov 9, 2011, at 11:19 AM, Issac Goldstand wrote: Bring it (the key) tonight :) On 09/11/2011 11:12, Jim Jagielski wrote: 2010-11-04 is the day I created the new key… it's unexpired (at least from what I can see ;) ) On Nov 9, 2011, at 7:52 AM, Rainer Jung wrote: On 09.11.2011 07:43, Rainer Jung wrote: Hi Jim, it looks like your key expired last Friday? Oups, was so convinced it is new, that I didn't see it already expired a year ago. Maybe you should sign 2.4.0 with a new one? Rainer % gpg --verify ../incoming/httpd/trunk/2.3.15/httpd-2.3.15-beta.tar.gz.asc gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made November 9, 2011 3:20:26 PM CET using RSA key ID 791485A8 gpg: Good signature from Jim Jagielski (Release Signing Key) j...@apache.org gpg: aka Jim Jagielski j...@jimjag.com gpg: aka Jim Jagielski j...@jagunet.com % gpg --list-keys 791485A8 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/791485A8 2010-11-04 uid Jim Jagielski (Release Signing Key) j...@apache.org uid Jim Jagielski j...@jimjag.com uid Jim Jagielski j...@jagunet.com sub 4096R/9B6D9BF7 2010-11-04 Regards, Rainer
Re: [VOTE] Release 2.3.15-beta as beta
On 09.11.2011 11:12, Jim Jagielski wrote: 2010-11-04 is the day I created the new key… it's unexpired (at least from what I can see ;) ) Sorry for the noise, false alarm :( Regards, Rainer On Nov 9, 2011, at 7:52 AM, Rainer Jung wrote: On 09.11.2011 07:43, Rainer Jung wrote: Hi Jim, it looks like your key expired last Friday? Oups, was so convinced it is new, that I didn't see it already expired a year ago. Maybe you should sign 2.4.0 with a new one? Rainer % gpg --verify ../incoming/httpd/trunk/2.3.15/httpd-2.3.15-beta.tar.gz.asc gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made November 9, 2011 3:20:26 PM CET using RSA key ID 791485A8 gpg: Good signature from Jim Jagielski (Release Signing Key) j...@apache.org gpg: aka Jim Jagielskij...@jimjag.com gpg: aka Jim Jagielskij...@jagunet.com % gpg --list-keys 791485A8 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/791485A8 2010-11-04 uid Jim Jagielski (Release Signing Key)j...@apache.org uid Jim Jagielskij...@jimjag.com uid Jim Jagielskij...@jagunet.com sub 4096R/9B6D9BF7 2010-11-04 Regards, Rainer
Re: [VOTE] Release 2.3.15-beta as beta
On Wed, Nov 9, 2011 at 6:24 AM, Jim Jagielski j...@jagunet.com wrote: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... Is anyone seeing this? Test Summary Report --- t/modules/cgi.t (Wstat: 0 Tests: 53 Failed: 0) Parse errors: Bad plan. You planned 58 tests but ran 53. t/modules/proxy.t (Wstat: 0 Tests: 15 Failed: 2) Failed tests: 9-10
Re: [VOTE] Release 2.3.15-beta as beta
Am 09.11.2011 15:24, schrieb Jim Jagielski: The 2.3.15-beta (prerelease) tarballs are available for download at test: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as 2.3.15-beta BETA and, with luck, this will be our last beta and the next release in ~2weeks or less will be 2.4.0 GA!! Vote will last the normal 72 hours... I believe Eric added some SSL stuff to mod_lua, and this now causes at 1st glance that it doesnt compile at least for NetWare, and most likely also not for Windows (static makefiles need to be fixed); but in addition I think we need to make this SSL stuff optional so that its possible to build a mod_lua without SSL support. Gün.
Re: [VOTE] Release 2.3.15-beta as beta
I believe Eric added some SSL stuff to mod_lua, and this now causes at 1st glance that it doesnt compile at least for NetWare, and most likely also not for Windows (static makefiles need to be fixed); but in addition I think we need to make this SSL stuff optional so that its possible to build a mod_lua without SSL support. It's just wrapping an existing mod_ssl optional function (mod_proxy does the same, but maybe I've flubbed a bit?) -- so I don't think it needs to be supressable.
Re: [VOTE] Release 2.3.15-beta as beta
Am 10.11.2011 00:09, schrieb Eric Covener: I believe Eric added some SSL stuff to mod_lua, and this now causes at 1st glance that it doesnt compile at least for NetWare, and most likely also not for Windows (static makefiles need to be fixed); but in addition I think we need to make this SSL stuff optional so that its possible to build a mod_lua without SSL support. It's just wrapping an existing mod_ssl optional function (mod_proxy does the same, but maybe I've flubbed a bit?) -- so I don't think it needs to be supressable. I didnt yet look self closer at it - just got the problem reported ... so I guess mod_lua doesnt use OpenSSL functions, and therefore doesnt link against OpenSSL, and loads runs still fine without mod_ssl loaded? Gün.
Re: [VOTE] Release 2.3.15-beta as beta
Am 10.11.2011 00:11, schrieb Guenter Knauf: I didnt yet look self closer at it - just got the problem reported ... so I guess mod_lua doesnt use OpenSSL functions, and therefore doesnt link against OpenSSL, and loads runs still fine without mod_ssl loaded? ok, adding include path seems to be enough - fixed in svn. Gün.
Re: [VOTE] Release 2.3.15-beta as beta
On Wed, Nov 9, 2011 at 1:24 PM, Jeff Trawick traw...@gmail.com wrote: Test Summary Report --- t/modules/cgi.t (Wstat: 0 Tests: 53 Failed: 0) Parse errors: Bad plan. You planned 58 tests but ran 53. t/modules/proxy.t (Wstat: 0 Tests: 15 Failed: 2) Failed tests: 9-10 This is probably new-os-install/perl-version syndrome. The t/modules/cgi.t has since disappeared, the request from t/modules/proxy.t that fails verification works fine outside of the framework.
