/**
     * User property key for cache configuration.
     *
     * @since 4.1.0
     */
    public static final String MAVEN_CACHE_CONFIG_PROPERTY = "maven.cache.config";

    /**
     * User property to enable cache statistics display at the end of the build.
     * When set to true, detailed cache statistics including hit/miss ratios,

  }

  /**
   * Invoked when a response will be served from the cache or network based on validating the
   * cached Response freshness. Will be followed by cacheHit or cacheMiss after the network
   * Response is available.
   *
   * This event will only be received when a Cache is configured for the client.
   */
  open fun cacheConditionalHit(
    call: Call,
    cachedResponse: Response,
  ) {
  }

    }

    @Test
    public void test_store_triggersIndexing_whenCacheSizeExceeded() {
        // Set small cache size
        indexUpdateCallback.maxDocumentCacheSize = 1;

        DataStoreParams paramMap = new DataStoreParams();

        // Add first document - should trigger indexing because cache size is 1
        Map<String, Object> dataMap1 = new HashMap<>();
        dataMap1.put("url", "http://example.com/test1");

         * It's very unlikely that any loaded Futures class will see getChecked called with more
         * than a handful of exceptions. But it seems prudent to set a cap on how many we'll cache.
         * This avoids out-of-control memory consumption, and it keeps the cache from growing so
         * large that doing the lookup is noticeably slower than redoing the work would be.
         *

		newCache.buildUserGroupMemberships()
	}

	cache := store.lock()
	defer store.unlock()

	// We should only update the in-memory cache if there were no changes
	// to the in-memory cache since the disk loading began. If there
	// were changes to the in-memory cache we should wait for the next
	// cycle until we can safely update the in-memory cache.
	//
	// An in-memory cache must be replaced only if we know for sure that the

    protected CrawlerClientFactory crawlerClientFactory;

    /**
     * List of URLs to be deleted, cached for batch processing.
     * All access is synchronized via indexUpdateCallback lock.
     */
    protected List<String> deleteUrlList = new ArrayList<>();

    /** Maximum size of the delete URL cache before batch deletion is triggered. */
    protected int maxDeleteDocumentCacheSize;

            log.trace("Have DC referral " + dr);
        }

        if (dr != null && domain.equals(dr.getServer()) && root.equals(dr.getShare())) {
            // If we do cache these we never get to the properly cached
            // standalone referral we might have.
            log.warn("Dropping self-referential referral " + dr);
            dr = null;
        }
        return dr;
    }

    /**

## Version 4.1.1

_2019-09-05_

 *  Fix: Don't drop repeated headers when validating cached responses. In our Kotlin upgrade we
    introduced a regression where we iterated the number of unique header names rather than then
    number of unique headers. If you're using OkHttp's response cache this may impact you.


## Version 4.1.0

_2019-08-12_

 [brotli]: https://github.com/google/brotli

labels.file_auth_scheme_ftp=FTP
labels.pagination_page_guide_msg={0}/{1} ({2} éléments)
labels.list_could_not_find_crud_table=Non enregistré.
labels.scheduledjob_configuration=Planificateur de tâches
labels.scheduledjob_title_details=Tâche
labels.scheduledjob_name=Nom
labels.scheduledjob_target=Cible
labels.scheduledjob_status=Statut
labels.scheduledjob_cronExpression=Planification
labels.scheduledjob_scriptType=Méthode d'exécution

import org.lastaflute.web.response.ActionResponse;
import org.lastaflute.web.response.HtmlResponse;
import org.lastaflute.web.util.LaRequestUtil;

import com.google.common.cache.Cache;
import com.google.common.cache.CacheBuilder;
import com.microsoft.aad.msal4j.AuthorizationCodeParameters;
import com.microsoft.aad.msal4j.ConfidentialClientApplication;
import com.microsoft.aad.msal4j.IAuthenticationResult;