| -Original Message-
| I suppose you're talking about chunked encoding on the input ?
Yep.
| The current mechanism is not the best - we shouldn't use Content-Length,
| but let the connector signal the end of the stream.
Yes, exactly. Both request and the facade input stream take an
On Thu, 23 Aug 2001, Keith Wannamaker wrote:
I think ajp is handling the missing content length case OK, except we
might need to send an initial body chunk even if contentlength is not
specified.
I was hoping to get it in tc 3.3 since tc is not quite doing what one
would expect from
I think ajp is handling the missing content length case OK, except we
might need to send an initial body chunk even if contentlength is not
specified.
I was hoping to get it in tc 3.3 since tc is not quite doing what one
would expect from reading the spec. How about I post a diff
for
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 10:21 AM
To: [EMAIL PROTECTED]
Subject: RE: ajp13, tc 3.3
On Thu, 23 Aug 2001, Keith Wannamaker wrote:
I think ajp is handling the missing content length case OK,
except
On Thu, 23 Aug 2001, Larry Isaacs wrote:
length, not no
content. It should be a simple change, we just must make sure
we check all
places where ContentLength is used and fix it everywhere.
To make sure I am in sync, exactly which spec are you refering to.
Thanks.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 12:59 PM
To: '[EMAIL PROTECTED]'
Subject: RE: ajp13, tc 3.3
On Thu, 23 Aug 2001, Larry Isaacs wrote:
length, not no
content. It should be a simple change, we just must
I want to be able to support chunked encoding through ajpv13
in TC 3.3. Apache decodes the body for us, it is only a matter
of making the distinction between an unknown content-length
an a zero content-length. Costin I'd like to tweak what
you did here.. do you have an opinion on the matter?
