minio-4.0.8.tar minio/Chart.yaml apiVersion: v1 appVersion: RELEASE.2022-07-29T19-40-48Z description: Multi-Cloud Object Storage home: https://min.io icon: https://min.io/resources/img/logo/MINIO_wordmark.png keywords: - minio - storage - object-storage - s3 - cluster maintainers: - email: ******@****.*** name: MinIO, Inc name: minio sources: - https://github.com/minio/minio version: 4.0.8 minio/values.yaml ## Provide a name in place of minio for `app:` labels ## nameOverride: "" ## Provide a name...

  </error-page>
  <error-page>
    <error-code>404</error-code>
    <location>/WEB-INF/view/error/redirect.jsp?type=notFound</location>
  </error-page>
  <error-page>
    <error-code>408</error-code>
    <location>/WEB-INF/view/error/redirect.jsp?type=logOut</location>
  </error-page>
  <error-page>
    <error-code>500</error-code>
    <location>/WEB-INF/view/error/redirect.jsp?type=systemError</location>

        return buildRedirectRequest(userResponse, method)
      }

      HTTP_CLIENT_TIMEOUT -> {
        // 408's are rare in practice, but some servers like HAProxy use this response code. The
        // spec says that we may repeat the request without modifications. Modern browsers also
        // repeat the request (even non-idempotent ones.)

    val response = client.newCall(request).execute()
    assertThat(response.code).isEqualTo(408)
    assertThat(response.body.string()).isEqualTo("You took too long!")
  }

  @Test
  fun maxClientRequestTimeoutRetries() {
    server.enqueue(
      MockResponse(
        code = 408,
        headers = headersOf("Connection", "Close"),
        body = "You took too long!",

   * due to any of:
   *
   *  * A stale connection. The request was made on a reused connection and that reused connection
   *    has since been closed by the server.
   *  * A client timeout (HTTP 408).
   *  * A authorization challenge (HTTP 401 and 407) that is satisfied by the [Authenticator].
   *  * A retryable server failure (HTTP 503 with a `Retry-After: 0` response header).

    was shutting down.
 *  Fix: Honor `OkHttpClient.retryOnConnectionFailure()` when the response is a
    HTTP 408 Request Timeout. If retries are enabled, OkHttp will retry exactly
    once in response to a 408.
 *  Fix: Don't crash when reading the empty `HEAD` response body if it specifies
    a `Content-Length`.
 *  Fix: Don't crash if the thread is interrupted while reading the public

    if (responseCode == HttpURLConnection.HTTP_CLIENT_TIMEOUT) {
      // 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()

      "Expected HTTP 101 response but was '404 Not Found'",
    )
  }

  @Test
  fun clientTimeoutClosesBody() {
    webServer.enqueue(
      MockResponse.Builder()
        .code(408)
        .build(),
    )
    webServer.enqueue(
      MockResponse.Builder()
        .webSocketUpgrade(serverListener)
        .build(),
    )
    val webSocket: WebSocket = newWebSocket()

  integrity sha512-knxG2q4UC3u8stRGyAVJCOdxFmv5DZiRcdlIaAQXAbSfJya+OhopNotLQrstBhququ4ZpuKbDc/8S6mgXgPFPw==

isbinaryfile@^4.0.8:
  version "4.0.10"
  resolved "https://registry.yarnpkg.com/isbinaryfile/-/isbinaryfile-4.0.10.tgz#0c5b5e30c2557a2f06febd37b7322946aaee42b3"

    maintainers:
    - email: ******@****.***
      name: MinIO, Inc
    name: minio
    sources:
    - https://github.com/minio/minio
    urls:
    - https://charts.min.io/helm-releases/minio-4.0.8.tgz
    version: 4.0.8
  - apiVersion: v1
    appVersion: RELEASE.2022-07-26T00-53-03Z
    created: "2024-10-11T14:15:09.765514151+02:00"
    description: Multi-Cloud Object Storage