Re: Re: HTTP doesn't work after upgrading from 2.0.55 to 2.2.15

[Chen Chien-Yu <honercek@xxxxxxxxx>]

Hi William,

I've ever mentioned if I comment out the "Listen 443" and leave only the "Listen 80", the client can get the page without problem via HTTP. (In this successful case, I also see the two 0 and 5 length bucket, don't know why they are sent out even reach the EOS)

The problem only exists  via HTTP when the "Listen 443" and "Listen 80" coexist.

Browser is always fine in both case if I use HTTPS.

As the questions you said, I have to see what the answer are..but not sure if I can figure them out.

Thanks

Best regards,

honercek

On Fri, May 28, 2010 at 12:14 PM, William A. Rowe Jr. <wrowe@xxxxxxxxxxxxx> wrote:

On 5/27/2010 11:04 PM, Chen Chien-Yu wrote:
> Hi William,
>
> Refer to your words, so it's a bug in the bucket brigade mechanism?
> Should I report it to the Apache bug system?
> The two buckets are processed in the ap_core_output_filter(), and in the
> case of EOS bucket (APR_BUCKET_IS_EOS is true)
> That's why, the specific two buckets aren't sent out anymore..?!

There is no bug in the core, when EOS is hit, that's it.

What module creates this missing 5 byte bucket?  Was it a 0 len chunk header?
If that never hits the wire, it sounds like it could be a bug, but I've seen
no other reports of similar buggy behavior in 2.2.15, so I tend to suspect a
module, and most likely an external one.