[jira] [Updated] (WAGON-570) Use RedirectStrategy from HttpClient rather than a custom approach

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WAGON-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated WAGON-570:
---------------------------------
    Summary: Use RedirectStrategy from HttpClient rather than a custom approach  (was: Use RedirectStrategy from HttpClient rather than our custom code)

> Use RedirectStrategy from HttpClient rather than a custom approach
> ------------------------------------------------------------------
>
>                 Key: WAGON-570
>                 URL: https://issues.apache.org/jira/browse/WAGON-570
>             Project: Maven Wagon
>          Issue Type: Improvement
>          Components: wagon-http
>    Affects Versions: 3.3.3
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.4.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.



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