[
https://issues.apache.org/jira/browse/WAGON-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-570.
--------------------------------
Resolution: Fixed
Fixed with
[e9dd77479834bfe24162be1fc983505000c3fe26|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=e9dd77479834bfe24162be1fc983505000c3fe26].
> 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)
