Currently, the zipType option specified in topcat.json downloadTransportType is effectively ignored. We received a user feedback asking us why we weren't compressing HTTPS downloads, and Chris explained that previously this wasn't enabled due to load on the IDS machine, but perhaps this should be re-evaluated. At the very least, since we have a config option we should allow this option to actually configure the calls to the IDS.
Note: this will likely involve adding a zipType property to the Download entity (and hence a database schema change) to enable the StatusCheck call to prepareData to use the config option.