community edition negotiating snappy, setting bit when it should not

Per a discussion in the forums, a user who has CE 6.0.0 and the Java SDK is seeing items come across the wire with the snappy compression bit set.

The client code is pretty clear, it shouldn't be possible to attempt decompression unless this bit is set. It is not verified, but it looks like the bit is set in some responses, which should not happen when using CE. It also looks like the payload is not compressed, as the snappy library does not like the payload.

This is not yet verified internally, but the user can reproduce it at will. When time allows, Graham Pople is attempting reproduction.

I'm filing this as a quick code inspection may be in order to see if there is a way we see this bit could erroneously be set. I do not know it to impact Mad Hatter, but it's reasonable that it might since this area hasn't to my knowledge changed much since 6.0.