nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-2716) protocol-http: Response headers are not stored for a compressed response
Date Fri, 24 May 2019 13:56:00 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847564#comment-16847564
] 

Hudson commented on NUTCH-2716:
-------------------------------

SUCCESS: Integrated in Jenkins build Nutch-trunk #3625 (See [https://builds.apache.org/job/Nutch-trunk/3625/])
NUTCH-2716 Response headers are not stored for a compressed response (snagel: [https://github.com/apache/nutch/commit/2fce5cdb41f6b838ab2e4e29932792672290bf5b])
* (edit) src/plugin/protocol-htmlunit/src/java/org/apache/nutch/protocol/htmlunit/HttpResponse.java
* (edit) src/plugin/protocol-selenium/src/java/org/apache/nutch/protocol/selenium/HttpResponse.java
* (edit) src/java/org/apache/nutch/tools/warc/WARCExporter.java
* (edit) src/plugin/protocol-http/src/java/org/apache/nutch/protocol/http/HttpResponse.java
* (edit) src/java/org/apache/nutch/tools/CommonCrawlFormatWARC.java
* (edit) src/java/org/apache/nutch/tools/WARCUtils.java
* (edit) src/plugin/lib-htmlunit/ivy.xml


> protocol-http: Response headers are not stored for a compressed response
> ------------------------------------------------------------------------
>
>                 Key: NUTCH-2716
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2716
>             Project: Nutch
>          Issue Type: Bug
>          Components: protocol
>    Affects Versions: 1.15
>            Reporter: Yossi Tamari
>            Assignee: Sebastian Nagel
>            Priority: Major
>             Fix For: 1.16
>
>
> Even when store.http.headers=true, the HTTP headers are not saved for a gzipped or deflated
response, because they may contain an incorrect content-length header.
> This causes WARCExporter to generate "resource" (headerless) entries instead of "response"
entries.
> While I can see why reporting the wrong content-encoding and length may be a bug, removing
all the headers is not a fix.
> I am not submitting a patch yet since I'm not sure what the best fix is, but I guess
the best patch is to remove those two header lines and store the rest of the headers. If there
is no objection, I can submit a patch that does this. Otherwise, what would be a better fix?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message