Hi,

Protocol-http does this (not storing HTTP response heades if response is
compressed):

          // store the headers verbatim only if the response was not
compressed
          // as the content length reported does not match otherwise
          if (httpHeaders != null) {
            headers.add(Response.RESPONSE_HEADERS, httpHeaders.toString());
          }
          if (Http.LOG.isTraceEnabled()) {
            Http.LOG.trace("fetched " + content.length + " bytes from " +
url);
          }

And i do not agree with it. Almost all content is compressed now, so this
will never work. We need the headers and response code stored for WARC
export and do not care about an incorrect length header.

Before patching this up and breaking that code out of the compression
condition, i do ask myself, is that a good idea? I don't see okhttp having
the same condition.

Markus

Reply via email to