I have a problem of TrafficServer with a transform plugin in place returning an erroneous Content-Length of zero. An equivalent GET returns a correct Content-Length value, as do both GET and HEAD without the plugin.
I think this looks like a problem of TrafficServer rather than of the plugin. Of course with a transformation in place we can't rely on the Content-Length from the backend, but in the case of a HEAD or a no-content response (204/304) we need to unset it, not set an incorrect value. We've had (and fixed) similar issues with HTTPD in the past. Omitting Content-Length is acceptable: it's a violation of a SHOULD not a MUST. Setting it incorrectly is broken. It should be possible to reproduce this with the bundled null-transform example. NOTE: this appears to be an entirely separate issue to returning 304, as described in my previous email. The 304 responses were observed with no plugin; the zero Content-Length appears to be triggered by a plugin. -- Nick Kew
