On 10/17/07, Nick Kew <[EMAIL PROTECTED]> wrote:
> Can I suggest your best course of action now is to enter it into
> our bugzilla at http://issues.apache.org/ ? I *think* the root
> cause of this is related to bugs 16518 and 19442 and an old/
> incorrect fix to them (see Comment 14 on bug 16518).
On Tue, 16 Oct 2007 14:42:40 -0700
"Ragini Bisarya" <[EMAIL PROTECTED]> wrote:
> I would like to clarify that the client does not know if the web
Yes, I understand what you're saying. That was clear enough first
time. And just to be clear, I believe you're probably right that
there is a problem
Thanks for your response.
I would like to clarify that the client does not know if the web
resource is protected by authentication or not and if so, does it
require Basic or Digest authentication scheme. Therefore the client
can never send the authentication header in the initial request.
The aim
On Mon, 15 Oct 2007 18:15:42 -0700
"Ragini Bisarya" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I see a difference in the way Apache responds to a Expect:
> 100-continue header in version 1.3.33 vs 2.2.6. The 1.3.33 handling is
> correct. I feel the 2.2.6 handling is a bug.
>
> For PUT requests with a
Hi,
I see a difference in the way Apache responds to a Expect:
100-continue header in version 1.3.33 vs 2.2.6. The 1.3.33 handling is
correct. I feel the 2.2.6 handling is a bug.
For PUT requests with a Expect: 100-continue header, Apache 2.2.6
server sends a HTTP/1.1 100 Continue response before
