There seems to be some consensus that we should add a key to r-notes
as a temporary fix ( at least till 2.4 ). Hence, I'm attaching a patch
- ap_meets_conditions_fixes.patch, with the appropriate fixes to
ap_meets_conditions() using resource-exists key for this purpose.
To be sure that we do not
Paritosh Shah wrote:
Thanks for the patches ... I'll take a look when I get some time.
I used resource-exists as the key instead of
NON_EXTANT_RESOURCE or NO_RESOURCE as suggested by Chris Darroch,
to avoid double negatives.
I wanted to use such a term because the default case, when a
That's why!! Thank you Nick.
On 10/19/07, Nick Kew [EMAIL PROTECTED] wrote:
On Fri, 19 Oct 2007 10:49:27 +0200
Alexander Farber [EMAIL PROTECTED] wrote:
the libapreq calls util_read() function -
http://search.cpan.org/src/DOUGM/libapreq-0.31/c/apache_request.c
which allocates a buffer
Alexander Farber wrote:
Hello,
the libapreq calls util_read() function -
http://search.cpan.org/src/DOUGM/libapreq-0.31/c/apache_request.c
which allocates a buffer with (r-remaining + 1) bytes.
Then it reads up to r-remaining bytes by calling
ap_get_client_block() and memcpy() repeatedly.
As Steve Marquess recently mentioned I've been working on a patch to
implement OCSP stapling support for mod_ssl.
The first version of OpenSSL which will support OCSP stapling will now
be 0.9.8h not 0.9.8g as originally announced.
It has been suggested a performing OCSP queries via the sub
As Steve Marquess recently mentioned I've been working on a patch to
implement OCSP stapling support for mod_ssl.
The first version of OpenSSL which will support OCSP stapling will now
be 0.9.8h not 0.9.8g as originally announced.
It has been suggested a performing OCSP queries via the sub
Hello,
the libapreq calls util_read() function -
http://search.cpan.org/src/DOUGM/libapreq-0.31/c/apache_request.c
which allocates a buffer with (r-remaining + 1) bytes.
Then it reads up to r-remaining bytes by calling
ap_get_client_block() and memcpy() repeatedly.
Neither util_read(), nor
Hello,
I think it is a bug in the libapreq-1.33:
util_read() doesn't 0-terminate the received POST data,
but after that calls ap_getword() on it repeatedly.
Regards
Alex
--
http://preferans.de
On Fri, 19 Oct 2007 10:49:27 +0200
Alexander Farber [EMAIL PROTECTED] wrote:
Hello,
the libapreq calls util_read() function -
http://search.cpan.org/src/DOUGM/libapreq-0.31/c/apache_request.c
which allocates a buffer with (r-remaining + 1) bytes.
That looks like very, very old and obsolete
