To minimize reporting noise (in javascript console, in UMA and UKM data) XSDB shouldn't "block" *empty* responses (not just empty 204s, but also empty 200s and other http responses).
I think gathering the data on Content-Length should be sufficient to mark this bug as fixed. Also note that even responses with an empty body need to be "blocked" by stripping down their non-safelisted-headers.
Comment 1 by lukasza@chromium.org
, Feb 5 2018