help

Re: Is 2.2.x broken?

The fix is the thing I just added to STATUS today On Tue, Dec 6, 2016 at 1:07 PM, Jacob Champion wrote: > I'm trying to test a backport to the 2.2.x tip, but it looks like r1758671 > might have busted our request parsing. Every test we have fails; I think > ap_rgetline() is

Re: Is 2.2.x broken?

An associated patch was likely overlooked, please go ahead and revert. On Dec 6, 2016 12:07 PM, "Jacob Champion" wrote: > I'm trying to test a backport to the 2.2.x tip, but it looks like r1758671 > might have busted our request parsing. Every test we have fails; I think

Is 2.2.x broken?

I'm trying to test a backport to the 2.2.x tip, but it looks like r1758671 might have busted our request parsing. Every test we have fails; I think ap_rgetline() is no longer dealing with the final CRLF line correctly. Reverting that commit fixes things. Can anyone confirm that it's not just

Re: Content-Length header for HTTP 204 and 1xx status codes

Hi Yann, 2016-12-05 13:54 GMT+01:00 Yann Ylavic : > Hi Luca, > > sorry for the delay (overwhelmed these times)... > thanks a lot for the help! > > On Mon, Dec 5, 2016 at 1:21 PM, Luca Toscano > wrote: > > > > > > 2016-11-30 18:46 GMT+01:00 Luca