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

ASF GitHub Bot commented on NUTCH-2763:
---------------------------------------

sebastian-nagel commented on pull request #498: NUTCH-2763 protocol-okhttp 
(store.http.headers): add whitespace in status line after status code also when 
message is empty
URL: https://github.com/apache/nutch/pull/498
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> protocol-okhttp (store.http.headers): add whitespace in status line after 
> status code also when message is empty
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: NUTCH-2763
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2763
>             Project: Nutch
>          Issue Type: Bug
>          Components: plugin, protocol
>    Affects Versions: 1.16
>            Reporter: Sebastian Nagel
>            Assignee: Sebastian Nagel
>            Priority: Minor
>             Fix For: 1.17
>
>
> [RFC 7230|https://tools.ietf.org/html/rfc7230#section-3.1.2] describes the 
> HTTP response status line as:
> {noformat}
> status-line = HTTP-version SP status-code SP reason-phrase CRLF
> {noformat}
> The "reason-phrase" is allowed to be empty, but the white space between 
> status-code and reason-phrase is mandatory. The  protocol-okhttp, when 
> storing the HTTP response header (store.http.headers = true), does not add a 
> white space when the message is empty, even if the original response header 
> contained a white space after the status code.
> Note: protocol-http add the status line literally.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to