[WAGON-570] Use RedirectStrategy from HttpClient rather than a custom approach

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.3
• Fix Version/s: 3.4.0
• Component/s: wagon-http
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 28/Oct/19 14:01
• Updated: 22/Feb/20 13:12
• Resolved: 22/Feb/20 13:11

Description

We have a custom implementation where we follow relocations for status codes 3xx. We can leverage RedirectStrategy implementations instead doing this on our own.

WAGON-568 revealed a very serious bug in our codebase. We blindly assume that requests can always be retried, regardless whether the HttpEntity is repeatable or not. This can lead to a lockup of the transport because we advertise a content length on input streams, but cannot deliver those bytes. It will block until the server sends a 408.

Issue Links

• links to: GitHub Pull Request #62