Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for tools (0.12 sec)

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

        assertThat(base.resolve("ht-tp//b/")).isEqualTo(parse("http://a/ht-tp//b/"))
        assertThat(base.resolve("ht.tp//b/")).isEqualTo(parse("http://a/ht.tp//b/"))
      }
    
      /**
       * https://tools.ietf.org/html/rfc3986#section-5.4.1
       */
      @Test
      fun rfc3886NormalExamples() {
        val url = parse("http://a/b/c/d;p?q")
        // No 'g:' scheme in HttpUrl.
        assertThat(url.resolve("g:h")).isNull()
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 67.9K bytes
    - Viewed (0)
  2. okhttp/src/main/kotlin/okhttp3/OkHttpClient.kt

         * the server responds with `HTTP/1.0`, that will be exposed by [Response.protocol].
         *
         * [alpn]: http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg
         * [rfc_2616]: http://www.w3.org/Protocols/rfc2616/rfc2616.html
         * [rfc_7540]: https://tools.ietf.org/html/rfc7540
         * [rfc_7540_34]: https://tools.ietf.org/html/rfc7540#section-3.4
         *
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sat Apr 06 04:21:33 GMT 2024
    - 52K bytes
    - Viewed (0)
  3. docs/changelogs/changelog_3x.md

        In OkHttp 3.x, each new `OkHttpClient` gets its own private connection pool.
        Applications should avoid creating many connection pools as doing so
        prevents connection reuse. Each connection pool holds its own set of
        connections alive so applications that have many pools also risk exhausting
        memory!
    
        The best practice in OkHttp 3 is to create a single OkHttpClient instance
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sun Feb 06 14:55:54 GMT 2022
    - 50.8K bytes
    - Viewed (0)
Back to top