compressed content in a http response

Now I feel an http response may be a zip containing multiple files. The response "body" will be an compressed bytes array. (To avoid confusion, I will call this a "zip" rather than a "file".) When you parse these bytes, you may see multiple zip entries.

If you assume the entire zip is a single file and try to decompress/deflate it, it might fail. The output may be empty.

The http response also contains useful response headers. One of the headers would be content-type. The gzip and zip types seem to require different parsers.