Search Options

Results per page
Sort
Preferred Languages
Advance

Results 31 - 36 of 36 for Petry (0.15 sec)

  1. okhttp/src/test/java/okhttp3/CacheTest.kt

          // 408's are a bit of an outlier because we may repeat the request if we encounter this
          // response code. In this scenario, there are 2 responses: the initial 408 and then the 200
          // because of the retry. We just want to ensure the initial 408 isn't cached.
          expectedResponseCode = 200
          server.enqueue(
            MockResponse.Builder()
              .setHeader("Cache-Control", "no-store")
              .body("FGHIJ")
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Wed Apr 10 19:46:48 GMT 2024
    - 108.6K bytes
    - Viewed (0)
  2. okhttp/src/main/kotlin/okhttp3/internal/connection/ReusePlan.kt

      override fun connectTlsEtc() = error("already connected")
    
      override fun handleSuccess() = connection
    
      override fun cancel() = error("unexpected cancel")
    
      override fun retry() = error("unexpected retry")
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 1K bytes
    - Viewed (0)
  3. docs/recipes.md

        ```kotlin
        if (credential == response.request.header("Authorization")) {
          return null // If we already failed with these credentials, don't retry.
         }
        ```
    
        You may also skip the retry when you’ve hit an application-defined attempt limit:
    
        ```kotlin
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Fri Feb 18 08:52:22 GMT 2022
    - 40.2K bytes
    - Viewed (1)
  4. okhttp/src/test/java/okhttp3/internal/connection/FastFallbackExchangeFinderTest.kt

       *
       * We get plan0 and plan1 from the route planner.
       * We get plan2 as a follow-up to plan1, typically retry the same IP but different TLS.
       * We get plan3 as a retry of plan0, which was canceled when it lost the race.
       *
       * This test confirms that we prefer to do the TLS follow-up (plan2) before the TCP retry (plan3).
       * It also confirms we enforce the 250 ms delay in each race.
       */
      @Test
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Wed Apr 24 04:40:49 GMT 2024
    - 20.9K bytes
    - Viewed (0)
  5. okhttp/src/test/java/okhttp3/ConnectionCoalescingTest.kt

            .body("after misdirect")
            .build(),
        )
    
        // Seed the connection pool.
        assert200Http2Response(execute(url), server.hostName)
    
        // Use the coalesced connection which should retry on a fresh connection.
        val sanUrl =
          url.newBuilder()
            .host("san.com")
            .build()
        execute(sanUrl).use { response ->
          assertThat(response.code).isEqualTo(200)
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Jan 20 10:30:28 GMT 2024
    - 18.7K bytes
    - Viewed (0)
  6. okhttp/src/main/kotlin/okhttp3/internal/http2/Hpack.kt

          Header("max-forwards", ""),
          Header("proxy-authenticate", ""),
          Header("proxy-authorization", ""),
          Header("range", ""),
          Header("referer", ""),
          Header("refresh", ""),
          Header("retry-after", ""),
          Header("server", ""),
          Header("set-cookie", ""),
          Header("strict-transport-security", ""),
          Header("transfer-encoding", ""),
          Header("user-agent", ""),
          Header("vary", ""),
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 22.5K bytes
    - Viewed (1)
Back to top