http Response Structure Zipped - http

Question

I've been dabbling with the underlying client-server communications (cURL, browsers, and server responses, among a variety of others). I think at this point I understand the basic structure of a request and response:
Request:
(Method) (File) (Protocol)
(Headers)
(Empty)
(Body?)
Response:
(Protocol) (Code) (Meaning)
(Headers)
(Empty)
(Body?)
This was working fine until I sent compressed information. More precisely, I used gzip to send HTML in the response.
First, I'm using an updated version of Chrome to test -- and if I use a prebuilt HTTP server solution, gzip (In exactly the way I'm using it now) works fine.
In the 'Accept-Encoding' header sent from Chrome, it states that it will accept gzip. My guess is there's something specific I haven't run across yet (And haven't been able to find through searching).
All that said, here's the response:
HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: text/html
Content-Encoding: gzip
Content-Length: 205
(Zipped data...)
If I remove gzip and leave everything else exactly the same, this works fine. The Content-Length is the length of the zipped data, not the raw data, though I commented that out to make sure it wasn't doing something I wasn't expecting. Chrome doesn't 'require' Content-Length to figure out what it wants to do.
At one stage, I also had Content-Type: text/html; charset=utf-8 which didn't make a difference (Underneath the zip, the string is converted to utf-8 on the server).
Originally I zipped the headers and the body for consistency (And lowest-length). I figured it failed because the headers had to be visible to the browser to figure out the body would be zipped.
In both cases, however, Chrome displays "ERR_CONTENT_DECODING_FAILED" which is classic "We don't know how to decode the information."
Prior to trying to embed this into the same response, I sent the headers first and the body second, thinking that may be the best approach -- two different responses.
Chrome took this to mean the server was pushing downloadable content and entered an infinite acceptance loop, so clearly that wasn't the solution. In addition, the content it received wasn't used.
Technically, a normal web server would end the transmission after sending the second response, but I'm experimenting without that to better understand the connections.
Is there something I'm missing, or are there any thoughts on what might be going wrong?
Thanks!
Edit
The code is scattered out across various functions (I doubt anyone wants to look at ~300 lines), but I picked out the relevant pieces. Right before gzip, self.written is html.
const zipper = require('zlib');
push(value, callback)
{
this.socket.write(value, callback);
}
let self = this;
zipper.gzip(self.written, function(error, zipped)
{
self.setHeaders(
{
'Content-Encoding': 'gzip',
'Content-Length': zipped.length
});
self.getHeaderString(function(error, headers)
{
self.push(headers + zipped, callback);
});
});
When I console.log the final response: