Am 2020-02-18 um 10:50 schrieb Oleg Kalnichevski:
On Mon, 2020-02-17 at 15:29 +0100, Michael Osipov wrote:
Am 2020-02-17 um 14:11 schrieb Oleg Kalnichevski:
On Sun, 2020-02-16 at 23:30 +0100, Michael Osipov wrote:
Folks,
I am working again on some stuff in Maven Wagon, WAGON-570. After
some
tests I do not understand why this does not fail:
...
The supplied entity is non-repeatable, DefaultRedirectStrategy
has
been
instructed to retry the PUT for this case.
(
https://github.com/apache/maven-wagon/commit/58a646776fa4811090063360e80280e21287e92b
)
For some strange reason the PUT is retried although the entity is
unusable. The peer (server) fails with request timeout. I would
expect
this to behave like the RetryHandler. If it cannot be retried,
fail.
Michael
Hi Michael
I can take a look. Is there a test case I could run locally to
reproduce the defect?
Alright, I have now a reduced test case here:
https://home.apache.org/~michaelo/issues/httpclient-redirect/
The ZIP file contains a sample code RedirectMain.java which
reproduces
Wagon's behavior. Test2.java is a simple servlet running on tomcat
8.5.51 here and accepting GET and PUT requests. out.log contains the
output of HttpClient and the failure.
My expectation would be HttpClient to fail with an expecption that
the
request cannot be retried because the input stream has already been
consumed.
Michael
Michael
Could you also pack your server side code into a WAR, please? I have no
idea what I need to do about web-fragment.xml
Sure, I have uploaded webapp.war. Please deploy it as usual on Tomcat
and put it as JAR on Tomcat's classpath because the integrated valve
must be on Tomcat's classpath.
The perform a PUT to /webapp/repo/....
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
