Does anyone know anything about this?

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7966

I think this is the same as the showstopper entry in STATUS:

   * Incorrect Content-Range headers or invalid 416 HTTP responses
      if a filter such as INCLUDES changes the content length.  It may
      happen only when there are multiple output brigades.

Is this fixed in HEAD?  If not, I agree that this is a showstopper
for a 2.0.36 release.  I know that I couldn't reproduce PR 7966
when I looked at it, but I think daedalus could reproduce this.  

Greg?  Jeff?  -- justin

Reply via email to