https://bz.apache.org/bugzilla/show_bug.cgi?id=61222
Joe Orton <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #35322|0 |1 is obsolete| | --- Comment #17 from Joe Orton <[email protected]> --- Created attachment 35323 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35323&action=edit iteration #5 I rewrote the loop logic to be more explicit (I hope) in the handling of different bucket types, at least I can understand it properly now. Three specific cases I'm testing: 1) a CGI script which writes the header, sleeps, writes the body -- must see headers hit the network before waiting to read the body 2) the bug reported here -- must see no buffering 3) for a small fast CGI script with <8K output -- does get C-L on response ... plus running the test suite. I'm worried there are specific response brigades with FLUSH this is going to fail to produce C-L where we previously did, e.g. as simple as: HEAP FLUSH EOS will produced chunked output now. I think we could safely handling this by moving the "short-cut" case for EOS right before the apr_brigade_split_ex call? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
