[NUTCH-2557] protocol-http fails to follow redirections when an HTTP response body is invalid

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.14
• Fix Version/s: 1.15
• Assignee: Unassigned
• Reporter: Gerard Bouchar
• Created: 09/Apr/18 14:40
• Updated: 01/Oct/19 14:28
• Resolved: 12/Jun/18 19:07

Description

If a server sends a redirection (3XX status code, with a Location header), protocol-http tries to parse the HTTP response body anyway. Thus, if an error occurs while decoding the body, the redirection is not followed and the information is lost. Browsers follow the redirection and close the socket soon as they can.

• Example: this page is a redirection to its https version, with an HTTP body containing invalidly gzip encoded contents. Browsers follow the redirection, but nutch throws an error:

• • http://www.webarcelona.net/es/blog?page=2

 

The HttpResponse::getContent class can already return null. I think it should at least return null when parsing the HTTP response body fails.

Ideally, we would adopt the same behavior as browsers, and not even try parsing the body when the headers indicate a redirection.