Based on the code (read: no tests have been conducted), it looks like crau does not preserve transfer encoding in the HTTP responses. Instead, the data will be stored with transfer encoding stripped, but the headers will likely still contain e.g. a Transfer-Encoding: chunked header, which means that the playback of these WARCs requires special code to handle this mismatch. (The relevant section in the specification is 6.3.2 in both WARC/1.1 and WARC/1.0.)
Based on the code (read: no tests have been conducted), it looks like crau does not preserve transfer encoding in the HTTP responses. Instead, the data will be stored with transfer encoding stripped, but the headers will likely still contain e.g. a
Transfer-Encoding: chunkedheader, which means that the playback of these WARCs requires special code to handle this mismatch. (The relevant section in the specification is 6.3.2 in both WARC/1.1 and WARC/1.0.)