- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 21 for DeVries (0.17 sec)
-
okhttp/src/main/kotlin/okhttp3/Authenticator.kt
* both. * * Applications may configure OkHttp with an authenticator for origin servers, or proxy servers, * or both. * * ## Authentication Retries * * If your authentication may be flaky and requires retries you should apply some policy * to limit the retries by the class of errors and number of attempts. To get the number of * attempts to the current point use this function. * * ```java
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 5.5K bytes - Viewed (0) -
docs/features/events.md
![Events Diagram](../assets/images/******@****.***) ### Events with Retries and Follow-Ups OkHttp is resilient and can automatically recover from some connectivity failures. In this case, the `connectFailed()` event is not terminal and not followed by `callFailed()`. Event listeners will receive multiple events of the same type when retries are attempted.
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Sun Feb 06 02:19:09 GMT 2022 - 7.7K bytes - Viewed (0) -
mockwebserver/README.md
assertEquals("application/json; charset=utf-8", request.getHeader("Content-Type")); assertEquals("{}", request.getBody().readUtf8()); ``` #### Dispatcher By default MockWebServer uses a queue to specify a series of responses. Use a Dispatcher (`import okhttp3.mockwebserver.Dispatcher`) to handle requests using another policy. One natural policy is to dispatch on the request path.
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Sun Dec 17 15:34:10 GMT 2023 - 5K bytes - Viewed (1) -
docs/changelogs/changelog_4x.md
**This release fixes a severe bug where OkHttp incorrectly detected and recovered from unhealthy connections.** Stale or canceled connections were incorrectly attempted when they shouldn't have been, leading to rare cases of infinite retries. Please upgrade to this release! * Fix: don't return stale DNS entries in `DnsOverHttps`. We were caching DNS results indefinitely rather than the duration specified in the response's cache-control header.
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Wed Apr 17 13:25:31 GMT 2024 - 25.2K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/http/HttpHeaders.kt
Challenge( schemeName, Collections.singletonMap<String, String>(null, peek + "=".repeat(eqCount)), ), ) peek = null continue } // It's a series of parameter names and values. val parameters = mutableMapOf<String?, String>() eqCount += skipAll('='.code.toByte()) while (true) { if (peek == null) { peek = readToken()
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 7.2K bytes - Viewed (0) -
mockwebserver/src/main/kotlin/mockwebserver3/MockResponse.kt
apply { this.socketPolicy = socketPolicy } /** * Throttles the request reader and response writer to sleep for the given period after each * series of [bytesPerPeriod] bytes are transferred. Use this to simulate network behavior. */ fun throttleBody( bytesPerPeriod: Long, period: Long, unit: TimeUnit, ) = apply {
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Tue Jan 23 14:31:42 GMT 2024 - 13.3K bytes - Viewed (1) -
docs/assets/images/events_with_failures_and_retries@2x.png
events_with_failures_and_retries@2x.png...
PNG Image - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Sun Feb 06 02:19:09 GMT 2022 - 223.1K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/connection/RoutePlanner.kt
*/ package okhttp3.internal.connection import java.io.IOException import okhttp3.Address import okhttp3.HttpUrl /** * Policy on choosing which connection to use for an exchange and any retries that follow. This uses * the following strategies: * * 1. If the current call already has a connection that can satisfy the request it is used. Using
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Wed Dec 20 23:27:07 GMT 2023 - 4.2K bytes - Viewed (0) -
docs/features/interceptors.md
### Choosing between application and network interceptors Each interceptor chain has relative merits. **Application interceptors** * Don't need to worry about intermediate responses like redirects and retries. * Are always invoked once, even if the HTTP response is served from the cache. * Observe the application's original intent. Unconcerned with OkHttp-injected headers like `If-None-Match`.
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Sun Feb 06 02:19:09 GMT 2022 - 8.1K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/http/RetryAndFollowUpInterceptor.kt
* sent. */ private fun recover( e: IOException, call: RealCall, userRequest: Request, requestSendStarted: Boolean, ): Boolean { // The application layer has forbidden retries. if (!client.retryOnConnectionFailure) return false // We can't send the request body again. if (requestSendStarted && requestIsOneShot(e, userRequest)) return false // This exception is fatal.
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Mon Apr 15 13:24:48 GMT 2024 - 12.1K bytes - Viewed (4)