httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: Status of Bug # 39243
Date Sat, 03 Mar 2007 23:16:52 GMT
I'm contemplating an HTTP/1.1-only solution, available only if the client
is willing to present expect-header 100-continue, which would involve
no buffering.

Bill

Ruediger Pluem wrote:
> 
> On 03/03/2007 09:50 PM, Kevin wrote:
>> Hi List-
>>
>> This isn't a support question, so please don't ignore it.
>>
>> It's a legitimate dev-type question on the status of an open bug that I
>> don't see answers to on bugzilla at:
>>
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=39243
>>
>> Can anyone share any sort of status on this bug?
>>
>> I'm running into this bug with 2.2.3 and plone (as indicated in my
>> comment on bugzilla), and it really puts a huge damper on what I can do
>> with plone.
> 
>>>From your comments in bugzilla I am not really sure if you are working with client
> certificates (I see you talking about SSL in general only). And even if you are
> working with client certificates this only affects you in the case that you
> are using Directory or Location based client certificates which require a SSL renegotiation.
> Plus your POST request needs to be the first operation during your connection
> to this Location / Directory.
> 
>> Surely there are other people that are suffering consequences of this
>> bug, no?  How are you working around it?
>>
>> Are there any plans to resolve this any time soon?  I'm guessing it's
> 
> No, currently there are no plans to change this. Please have a look at
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39243#c3
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39243#c7
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39243#c14
> 
> for reasons.
> 
> Regards
> 
> RĂ¼diger
> 
> 
> 
> 


Mime
View raw message