Brandon Knitter wrote:
Attached and below. Let me know if this is considered large and I
should move this to a bugzilla issue. Only took us about 30 minutes to
apply it. Again, this is against 1.2.21!
It would be the best if you could open bugzilla issue, because
the patch is more the a
Will do, please give me a day.
--
-bk
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 11:27 AM
To: Brandon Knitter
Cc: Tomcat Users List
Subject: Re: JK ISAPI Filter and Keep-Alive/Chunked Encoding (a.k.a. Is
1.2.21 broken?)
Brandon
Brandon Knitter wrote:
In 1.2.21 I'm seeing absolutely no Keep-Alive is performed, even when
the content-length is known and the browser is sending a Connection:
Keep-Alive request.
Thoughts?
It's broken for IIS (wrong API usage).
1.2.22 is scheduled for a release next week.
You can find
I was looking over the 1.2.21 code and I'm finding hints that a
chunked Transfer-Encoding is being attempted:
\native\common\jk_service.h(138):
unsigned is_chunked;/* 1 if content length is unknown (chunked
rq) */
Is there a trick to getting keep-alive and chunked encoding turned on?
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 10:37 AM
To: Tomcat Users List
Subject: Re: JK ISAPI Filter and Keep-Alive/Chunked Encoding (a.k.a. Is
1.2.21 broken?)
Brandon Knitter wrote:
In 1.2.21 I'm seeing absolutely no Keep-Alive is performed
Brandon Knitter wrote:
I tried this, but still there was no chunked encoding in version 1.2.22.
You we speaking about Keep-Alive, not TE chunked.
We have patched 1.2.21 to allow for enabling of chunked encoding in the
ISAPI filter if you configure it to do so (registry entry). Would this
be
