On Mon, Apr 14, 2014 at 11:29 AM, Joe Orton jor...@redhat.com wrote:
On Mon, Apr 14, 2014 at 08:32:18AM -0400, Jeff Trawick wrote:
FWIW, I think it is reasonable to say This *is* a private mod_ssl
interface for the purposes of introducing some modularity within this
particular SSL/TLS
On Fri, Apr 4, 2014 at 4:30 PM, jaillet...@apache.org wrote:
Author: jailletc36
Date: Fri Apr 4 20:30:38 2014
New Revision: 1584896
URL: http://svn.apache.org/r1584896
Log:
Do not perform a p+= 7 that could go past the end of the buffer in case we
find a 'content' without a corresponding
On Apr 15, 2014, at 1:51 PM, yla...@apache.org wrote:
PATCHES PROPOSED TO BACKPORT FROM TRUNK:
@@ -136,6 +179,8 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
2.4.x patch: trunk works
http://people.apache.org/~jim/patches/uds-rewrite.patch
+1: jim, humbedooh
+
Hi,
AFAIK, no crash has ever been reported for that.
I just noted this while looking at PR56287 and found it odd.
A file such as:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
htmlhead
meta http-equiv=Conten contentheadbody/body/html
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
will trigger the scan past the end
On 4/15/2014 2:21 PM, Jim Jagielski wrote:
I can't recall... isn't the issue still being worked an
additional aspect of mod_rewrite and UDS; that is, a new
behavior to be added (or handled) rather than a broken
behavior.
That was my understanding, too
--
Daniel Ruggeri
On Wed, Apr 16, 2014 at 1:59 AM, Yann Ylavic ylavic@gmail.com wrote:
Oh, didn't mean to vote -1, just wanted to add a note on the stuff
being worked that could be integrated in the backport.
I am (re)working on this currently.
Oh, didn't mean to vote -1, just wanted to add a note on the stuff
being worked that could be integrated in the backport.
I can make another proposal anyway, sorry for the noise.
Corrected in r1587758.
On Tue, Apr 15, 2014 at 9:21 PM, Jim Jagielski j...@jagunet.com wrote:
On Apr 15, 2014, at
On 12.04.2014 12:41, Kaspar Brand wrote:
The Expecting: DH PARAMETERS error is probably a red herring - it's
most likely a leftover in the OpenSSL error stack after the
configuration of another certificate (we try to load DH parameters at
the end of ssl_init_server_certs, which in turn is
