[
https://issues.apache.org/jira/browse/NUTCH-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735183#comment-16735183
]
Hudson commented on NUTCH-2657:
-------------------------------
SUCCESS: Integrated in Jenkins build Nutch-trunk #3596 (See
[https://builds.apache.org/job/Nutch-trunk/3596/])
NUTCH-2657 Protocol-http to store HTTP response header with "\r\n" - (snagel:
[https://github.com/apache/nutch/commit/122648e92e336f2e3194bd53c4a90ab7d0100178])
* (edit)
src/plugin/protocol-http/src/java/org/apache/nutch/protocol/http/HttpResponse.java
> Protocol-http to store HTTP response header with "\r\n"
> -------------------------------------------------------
>
> Key: NUTCH-2657
> URL: https://issues.apache.org/jira/browse/NUTCH-2657
> Project: Nutch
> Issue Type: Improvement
> Components: protocol
> Affects Versions: 1.15
> Reporter: Sebastian Nagel
> Priority: Minor
> Fix For: 1.16
>
>
> The plugins protocol-http and protocol-okhttp allow to store the HTTP request
> and/or response headers in the response metadata. However, there is no
> consensus which line breaks ("\r\n" or "\n") are used between header lines
> and whether there is a trailing second line break at the end of the headers:
> while request headers are stored by both plugins with "\r\n" and two trailing
> "\r\n", the response headers are stored by protocol-http with "\n" and a
> single trailing line break. This is difficult to handle if the headers are
> required to be stored uniformly (I've created such a [nasty bug writing WARC
> files|https://github.com/commoncrawl/nutch/issues/5]).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
