jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ignasi Barrera <notificati...@github.com>
Subject Re: [jclouds] Don't retry unsafe HTTP methods in case of an IOException (d4fa115)
Date Mon, 26 Oct 2015 15:47:41 GMT
The problem with IOExceptions is that usually are thrown when the connection has been closed
or there is some issue in the http channel. In most situations you can't know if a retry is
correct or not, so the idempotent check makes perfect sense. WDYT? Mind opening a JIRA issue
to track this?

We could move the idempotent logic to the default `ioRetryHandler` implementation, and let
the Glacier API configure a custom one that did not take into account the method.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/commit/d4fa1159ac555212f5b978f6140b56b0ebdd49b4#commitcomment-13987812
Mime
View raw message