try with current cvs and 'SSLOptions +OptRenegotiate' configured.
with this option enabled, modssl will use the client cert from the ssl
session cache if one was not already sent by the client. in this case,
modssl will not need to read from the client since full renegotiation is
by-passed. t
> AFAIK, this situation isn't implemented yet for 2.x. Currently, the server
Yes, I got hit by the clue stick from Cliff. This is a special case
where mod_ssl wants to empty its input.
> > P.S. core_request_config->bb shouldn't be used at all.
>
> Oh, i see. May I ask for some general overv
Once upon a time Nathan Friess shaped the electrons to say...
> AFAIK, this situation isn't implemented yet for 2.x. Currently, the server
> just returns a 'forbidden' response. There's a long comment in
> modules/ssl/ssl_engine_kernel.c which explains it all. I'm running some
> scripts which
From: "Justin Erenkrantz" <[EMAIL PROTECTED]>
Sent: Monday, June 10, 2002 4:30 PM
> On Mon, Jun 10, 2002 at 04:20:06PM -0600, Nathan Friess wrote:
> > A while back I started working with the httpd sources in attempt to
create
> > the missing code for POSTing over SSL when renegotiation is required
On Mon, Jun 10, 2002 at 04:20:06PM -0600, Nathan Friess wrote:
> A while back I started working with the httpd sources in attempt to create
> the missing code for POSTing over SSL when renegotiation is required. I
> made the necessary changes, tested the code using several 1 to 30 megabyte
> bina
A while back I started working with the httpd sources in attempt to create
the missing code for POSTing over SSL when renegotiation is required. I
made the necessary changes, tested the code using several 1 to 30 megabyte
binary files, and it seems to work nicely.
The body is sucked up with ap_g
