if !isNetworkError(err) {
						bootLogOnceIf(context.Background(), fmt.Errorf("%s has incorrect configuration: %w", clnt, err), "incorrect_"+clnt.String())
						incorrectConfigs = append(incorrectConfigs, fmt.Errorf("%s has incorrect configuration: %w", clnt, err))
					} else {
						offlineEndpoints = append(offlineEndpoints, fmt.Errorf("%s is unreachable: %w", clnt, err))
					}

constraints.LuhnCheck.message = La somme de contrôle Luhn Modulo 11 de {value} est incorrecte.
constraints.Mod10Check.message = La somme de contrôle Modulo 10 de {value} est incorrecte.
constraints.Mod11Check.message = La somme de contrôle Modulo 11 de {value} est incorrecte.
constraints.ModCheck.message = La somme de contrôle {modType} de {value} est incorrecte.
constraints.NotBlank.message = {item} est requis.

constraints.LuhnCheck.message = La suma de comprobación Luhn Módulo 11 de {value} es incorrecta.
constraints.Mod10Check.message = La suma de comprobación Módulo 10 de {value} es incorrecta.
constraints.Mod11Check.message = La suma de comprobación Módulo 11 de {value} es incorrecta.
constraints.ModCheck.message = La suma de comprobación {modType} de {value} es incorrecta.
constraints.NotBlank.message = {item} no puede estar en blanco.

#### El tiempo de respuesta ayuda a los atacantes { #the-time-to-answer-helps-the-attackers }

En ese punto, al notar que el servidor tardó algunos microsegundos más en enviar el response "Nombre de usuario o contraseña incorrectos", los atacantes sabrán que acertaron en _algo_, algunas de las letras iniciales eran correctas.

Un ejemplo difícil de literales de string en fragmentos de código: `f"I like {'oranges' if orange else "apples"}"`

Hardcore: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Info

... Sin embargo, las comillas dentro de fragmentos de código deben quedarse tal cual.

////

Un exemple difficile de littéraux de chaîne dans des extraits de code : `f"I like {'oranges' if orange else "apples"}"`

Hardcore: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Info

... Cependant, les guillemets à l’intérieur des extraits de code doivent rester tels quels.

////

slices, and strings in most Go implementations,
such races can in turn lead to arbitrary memory corruption.
</p>

<p>
Examples of incorrect synchronization are given in the
“Incorrect synchronization” section below.
</p>

<p>
Examples of the limitations on implementations are given in the
“Incorrect compilation” section below.
</p>

<h2 id="synchronization">Synchronization</h2>

<h3 id="init">Initialization</h3>

	// code generated by the AEAD cipher.
	//
	// Here is an incorrect implementation of IsEncrypted:
	//
	//   return len(e) > 16 && !bytes.ContainsRune(e, '-')
	//
	// An encrypted ETag may contain some random bytes - e.g.
	// and nonce value. This nonce value may contain a '-'
	// just by its nature of being randomly generated.
	// The above implementation would incorrectly consider
	// such an ETag (with a nonce value containing a '-')

			wantErr: policyCondFailedErr,
		},
		{
			name:    "incorrect bucket name",
			fv:      defaultFormVals.Clone().Set("Bucket", "incorrect"),
			wantErr: policyCondFailedErr,
		},
		{
			name:    "incorrect ContentType",
			fv:      defaultFormVals.Clone().Set(xhttp.ContentType, "incorrect"),
			wantErr: policyCondFailedErr,
		},
		{
			name:    "incorrect X-Amz-Algorithm",

#### Yanıt süresi saldırganlara yardımcı olur { #the-time-to-answer-helps-the-attackers }