Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for confirmats (0.2 sec)

  1. okhttp/src/main/kotlin/okhttp3/CertificatePinner.kt

     */
    @Suppress("NAME_SHADOWING")
    class CertificatePinner internal constructor(
      val pins: Set<Pin>,
      internal val certificateChainCleaner: CertificateChainCleaner? = null,
    ) {
      /**
       * Confirms that at least one of the certificates pinned for `hostname` is in `peerCertificates`.
       * Does nothing if there are no certificates pinned for `hostname`. OkHttp calls this after a
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 14.2K bytes
    - Viewed (1)
  2. okhttp/src/test/java/okhttp3/internal/ws/WebSocketHttpTest.kt

        closeWebSockets(webSocket, server)
      }
    
      /**
       * We had a bug where web socket connections were leaked if the HTTP connection upgrade was not
       * successful. This test confirms that connections are released back to the connection pool!
       * https://github.com/square/okhttp/issues/4258
       */
      @Test
      @Throws(Exception::class)
      fun webSocketConnectionIsReleased() {
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sun Mar 31 17:16:15 GMT 2024
    - 35.2K bytes
    - Viewed (1)
  3. okhttp/src/main/kotlin/okhttp3/internal/connection/RealConnectionPool.kt

       * was acquired, or null if no connection was acquired. The acquired connection will also be
       * given to [connectionUser] who may (for example) assign it to a [RealCall.connection].
       *
       * This confirms the returned connection is healthy before returning it. If this encounters any
       * unhealthy connections in its search, this will clean them up.
       *
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 20 17:03:43 GMT 2024
    - 16.2K bytes
    - Viewed (0)
  4. okhttp/src/test/java/okhttp3/internal/connection/FastFallbackExchangeFinderTest.kt

       * 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
      fun tcpConnectionsRaceAfterTlsFails() {
        val plan0 = routePlanner.addPlan()
    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)
Back to top