It should be this way because if you have a Pydantic `ValidationError` in your *response* or anywhere in your code (not in the client's *request*), it's actually a bug in your code.

And while you fix it, your clients/users shouldn't have access to internal information about the error, as that could expose a security vulnerability.

### Override the `HTTPException` error handler

The same way, you can override the `HTTPException` handler.

}}{{ end }} {{- if eq .Values.gateway.type "gcs" }} {{- if .Values.gateway.gcs.serviceAccountFile }} service-account-file.json: {{ .Values.gateway.gcs.serviceAccountFile | b64enc }} {{- end }} {{- end }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

.Release.Name }} heritage: {{ .Release.Service }} type: Opaque data: rootUser: {{ include "minio.root.username" . | b64enc | quote }} rootPassword: {{ include "minio.root.password" . | b64enc | quote }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

.Release.Name }} heritage: {{ .Release.Service }} type: Opaque data: rootUser: {{ include "minio.root.username" . | b64enc | quote }} rootPassword: {{ include "minio.root.password" . | b64enc | quote }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

.Release.Name }} heritage: {{ .Release.Service }} type: Opaque data: rootUser: {{ include "minio.root.username" . | b64enc | quote }} rootPassword: {{ include "minio.root.password" . | b64enc | quote }} {{- if .Values.etcd.clientCert }} etcd_client.crt: {{ .Values.etcd.clientCert | toString | b64enc | quote }} {{- end }} {{- if .Values.etcd.clientCertKey }} etcd_client.key: {{ .Values.etcd.clientCertKey | toString | b64enc | quote }} {{- end }} {{- end }} minio/templates/securitycontextconst.yaml {{-...

    .build();

OkHttpClient client = new OkHttpClient.Builder()
    .connectionSpecs(Collections.singletonList(spec))
    .build();
```

### Debugging TLS Handshake Failures

The TLS handshake requires clients and servers to share a common TLS version and cipher suite. This
depends on the JVM or Android version, OkHttp version, and web server configuration. If there is no
common cipher suite and TLS version, your call will fail like this:

```

////

/// tip

Keep in mind that JSON only supports `str` as keys.

But Pydantic has automatic data conversion.

This means that, even though your API clients can only send strings as keys, as long as those strings contain pure integers, Pydantic will convert them and validate them.

And the `dict` you receive as `weights` will actually have `int` keys and `float` values.

///

				// There was error in the REST request, retry after sometime as probably the peer is down.
				time.Sleep(5 * time.Second)
			}
		}
	}()
}

// newPeerRestClients creates new peer clients.
// The two slices will point to the same clients,
// but 'all' will contain nil entry for local client.
// The 'all' slice will be in the same order across the cluster.

Na verdade é comum utilizar Requests *dentro* de uma aplicação FastAPI.

Ainda assim, FastAPI pegou alguma inspiração do Requests.

**Requests** é uma biblioteca para interagir com APIs (como um cliente), enquanto **FastAPI** é uma biblioteca para *construir* APIs (como um servidor).

Eles estão, mais ou menos, em pontas opostas, um complementando o outro.

	// JWT token for x-amz-security-token is signed with admin
	// secret key, temporary credentials become invalid if
	// server admin credentials change. This is done to ensure
	// that clients cannot decode the token using the temp
	// secret keys and generate an entirely new claim by essentially
	// hijacking the policies. We need to make sure that this is
	// based on admin credential such that token cannot be decoded