objInfo := fi.ToObjectInfo(bucket, object, versioned)

			evt := evalActionFromLifecycle(ctx, *lc, lr, rcfg, objInfo)
			switch {
			case evt.Action.DeleteRestored(): // if restored copy has expired,delete it synchronously
				applyExpiryOnTransitionedObject(ctx, newObjectLayerFn(), objInfo, evt, lcEventSrc_Heal)
				return false
			case evt.Action.Delete():

labels.incrementalCrawling=Vérifier la dernière modification
labels.errorCount=Nombre d'erreurs
labels.errorLog=Journal des erreurs
labels.errorName=Nom de l'erreur
labels.expiredTime=Date d'expiration
labels.expires=Expire
labels.failureCountThreshold=Seuil de nombre d'échecs
labels.fileConfigName=Nom de la configuration d'exploration de fichiers
labels.fileName=Nom de fichier
labels.handlerName=Nom du gestionnaire

        assertNotNull(WitnessRegistration.WitnessRegistrationState.UNREGISTERING);
        assertNotNull(WitnessRegistration.WitnessRegistrationState.FAILED);
        assertNotNull(WitnessRegistration.WitnessRegistrationState.EXPIRED);
    }

    @Test
    void testEnumToStringConversions() {
        // Test that enum toString methods work properly
        assertEquals("CLUSTER_WITNESS", WitnessServiceType.CLUSTER_WITNESS.toString());

* Pour le HTTPS, le serveur a besoin de "certificats" générés par une tierce partie.
    * Ces certificats sont en fait acquis auprès de la tierce partie, et non "générés".
* Les certificats ont une durée de vie.
    * Ils expirent.
    * Puis ils doivent être renouvelés et acquis à nouveau auprès de la tierce partie.
* Le cryptage de la connexion se fait au niveau du protocole TCP.
    * C'est une couche en dessous de HTTP.

        return asStream(id)//
                .header("Pragma", "no-cache")//
                .header("Cache-Control", "no-cache")//
                .header("Expires", "Thu, 01 Dec 1994 16:00:00 GMT")//
                .header("Content-Type", "application/x-ndjson")//
                .stream(out -> {

```
...
        "MetaUsr": {
         "X-Amz-Restore-Expiry-Days": "4",

- In `Compliance` mode, objects cannot be deleted by anyone until retention period has expired for the given version id. If user has governance bypass permissions, an object's retention date can be extended in `Compliance` mode.
- Once object lock configuration is set to a bucket

time="2020-07-12T20:45:50Z" level=info msg="config response types accepted: [code token id_token]"
time="2020-07-12T20:45:50Z" level=info msg="config using password grant connector: local"
time="2020-07-12T20:45:50Z" level=info msg="config signing keys expire after: 3h0m0s"
time="2020-07-12T20:45:50Z" level=info msg="config id tokens valid for: 3h0m0s"
time="2020-07-12T20:45:50Z" level=info msg="listening (http) on 0.0.0.0:5556"
```

### Configure MinIO server with Dex

     */
    @Size(max = 20)
    public String name;

    /**
     * The expiration time for the crawling session.
     * This field indicates when the crawling session should expire or be cleaned up.
     */
    public String expiredTime;

    /**
     * The timestamp when this crawling session was created.
     * Stored as a long value representing milliseconds since epoch.
     */

      },
      "created": {
        "type": "date",
        "format": "date_optional_time"
      },
      "timestamp": {
        "type": "date",
        "format": "date_optional_time"
      },
      "expires": {
        "type": "date",
        "format": "date_optional_time"
      },
      "digest": {
        "type": "text",
        "index": false
      },
      "doc_id": {
        "type": "keyword"