Content compression executors no longer remove headers from the original response message

[ok2c]

Presently the content compression executors remove headers content related headers from the original response message to make it consistent with properties of the content entity. This is conceptually wrong. The content entity associated with the response message has its own content properties (content-length, content-type, content-encoding, etc) that can differ from those of the original message. As long as those properties correctly reflect the content produced be the entity there is no need to mutate the original response message itself, and there can be legitimate reasons for the caller to see the actual response headers.

I propose we change the content compression executors to stop removing content related headers from the original response message,

[arturobernalg]

• 1 Keeping the original response headers intact is more correct semantically

[arturobernalg]

LGTM