We are experiencing a problem with ap_get_client_block where a module
(Tomcat in this instance) is calling ap_get_client_block() to read stdin
and the last read (the one where we get back 0 bytes) is hanging for
Timeout time before returning. I did some investigation in http_protocol.c
in
On Mon, Jan 28, 2002 at 11:37:09AM -0600, RCHAPACH Rochester wrote:
We are experiencing a problem with ap_get_client_block where a module
(Tomcat in this instance) is calling ap_get_client_block() to read stdin
and the last read (the one where we get back 0 bytes) is hanging for
Timeout time
Justin Erenkrantz wrote:
On Mon, Jan 28, 2002 at 11:37:09AM -0600, RCHAPACH Rochester wrote:
We are experiencing a problem with ap_get_client_block where a module
(Tomcat in this instance) is calling ap_get_client_block() to read stdin
and the last read (the one where we get back 0
On Fri, Feb 01, 2002 at 12:55:48PM -0500, Greg Ames wrote:
h...chunked...it could be broken on ebcdic boxes now, due to the changes in
the input filtering and ap_getline. It used to be that every byte of inbound
http protocol data went thru ap_getline and got translated if the source code
Justin Erenkrantz wrote:
On Fri, Feb 01, 2002 at 12:55:48PM -0500, Greg Ames wrote:
h...chunked...it could be broken on ebcdic boxes now, due to the changes in
the input filtering and ap_getline. It used to be that every byte of inbound
http protocol data went thru ap_getline and
Greg Ames wrote:
Yeah, I think EBCDIC boxes may be broken in ap_rgetline. I posted
asking for people with those boxes to give feedback. No one
responded.
It might be a piece of cake fix. Is it true that inbound chunk headers no
longer go thru ap_[r]getline?
(yeah I know, find and
RCHAPACH Rochester wrote:
We are experiencing a problem with ap_get_client_block where a module
(Tomcat in this instance) is calling ap_get_client_block() to read stdin
and the last read (the one where we get back 0 bytes) is hanging for
Timeout time before returning.
Kent Bruinsma
So my post did show up... I thought it got lost, I sent it on Monday...
Strange delay factor...
I spent some additional time following the CVS's on this since last June
and figured out
what was going on. It is working, just not where I was initially looking.
The module that was
having this
