excon 1.7.3 → 1.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: f037a314897ce62c2905d8663cc3b340f8584aef13d8e28a61706033e282334b
4
- data.tar.gz: 1a7f16a08c9a5ac816236df1b434adc897d4644159c3a7f43ddfc5d8be4e8cc1
3
+ metadata.gz: 146bc7a814019dea02d71b4f8e93e3f9147360e96d0e4d12461947d1b55cd314
4
+ data.tar.gz: 97c4307814812b603328f89c7fe61f59a832a3cf08f5f1575a5337f493ea6314
5
5
  SHA512:
6
- metadata.gz: 82424d3a32813f3460c2e3ff55302a33004271a683b97a760c9eedaa009c42e859eca63ec55ef40fc71baacbab8ba1cb824878b074a6a814ff0782559347916f
7
- data.tar.gz: 91b7cb3ce4cb69dc7c935b16b891c854d5d7a4af83d1a013e05ca1e87783ef6f2d527d32862b15b98924e15f1203a361ee98a764b053cc592826dd1f7ba23e28
6
+ metadata.gz: 189a374b0e61e5ff832913c737a9a35a9c3b019819d7afdb4e6a207d434391e991c418cc0c881348cc0f9cc97b23068f685249822fb7213cb97b2df5c7ba5887
7
+ data.tar.gz: 375ec2dce1b5567f3f52b231d55820c5263135c2690425fe12ba9a764d3ef63675eefb3e34b64cb9dac8be0c4654771da24d7db0206e6d03b624a5a443ae0cbe
data/CONTRIBUTING.md CHANGED
@@ -9,6 +9,7 @@ New contributors are always welcome, when it doubt please ask questions. We stri
9
9
  * Review open [issues](https://github.com/excon/excon/issues) for things to help on.
10
10
  * [Create an issue](https://github.com/excon/excon/issues/new) to start a discussion on additions or features.
11
11
  * Fork the project, add your changes and tests to cover them in a topic branch.
12
+ * Tests go in `test/` (minitest), fixtures in `test/fixtures/`. See [AGENTS.md](AGENTS.md#tests).
12
13
  * Commit your changes and rebase against `excon/excon` to ensure everything is up to date.
13
14
  * [Submit a pull request](https://github.com/excon/excon/compare/).
14
15
 
data/README.md CHANGED
@@ -158,6 +158,8 @@ connection = Excon.new('https://...')
158
158
 
159
159
  You can modify timeouts and define whether and how many (blocking) retries Excon should attempt if errors occur.
160
160
 
161
+ Excon only retries requests marked `:idempotent`. Otherwise `:retry_limit`, `:retry_interval` and `:retry_errors` have no effect, whether they are set on the request, the connection or `Excon.defaults`.
162
+
161
163
  ```ruby
162
164
  # this request can be repeated safely, so retry on errors up to 4 times
163
165
  connection.request(:idempotent => true)
@@ -466,7 +468,7 @@ The #instrument method will be called for each HTTP request, response, retry, an
466
468
 
467
469
  For debugging purposes you can also use `Excon::StandardInstrumentor` to output all events to stderr. This can also be specified by setting the `EXCON_DEBUG` ENV var.
468
470
 
469
- See [the documentation for ActiveSupport::Notifications](http://api.rubyonrails.org/classes/ActiveSupport/Notifications.html) for more detail on using the subscription interface. See excon's [instrumentation_test.rb](https://github.com/excon/excon/blob/master/tests/middlewares/instrumentation_tests.rb) for more examples of instrumenting excon.
471
+ See [the documentation for ActiveSupport::Notifications](http://api.rubyonrails.org/classes/ActiveSupport/Notifications.html) for more detail on using the subscription interface. See excon's [instrumentation_test.rb](https://github.com/excon/excon/blob/master/test/middlewares/instrumentation_test.rb) for more examples of instrumenting excon.
470
472
 
471
473
  ## HTTPS client certificate
472
474