Play框架中的咖啡因缓存不返回缓存响应

Question

我在java Play Framework作业中使用Caffeine cache实现来缓存传出的http请求，我看到，尽管缓存已经启动并运行，但我的服务仍然每次都访问外部服务器，而不是返回缓存中的值。我看到记录在日志中的键总是相同的。

所以我看到FreshnessLifetime没有设置，所以这可能意味着缓存立即过期。但我仍然不知道如何在配置中设置它

我没有更改我的java代码，如果我需要这样做，我找不到任何示例，或者我只应该有一个用于所有传出请求的缓存配置。

在这方面我会很感激你的帮助

libraryDependencies += ws
libraryDependencies += caffeine

# Configuration settings for JSR 107 Cache for Play WS.
play.ws.cache {
  enabled = true
  heuristics.enabled = false
  name = "play-ws-cache"
}

# source https://github.com/ben-manes/caffeine/blob/master/jcache/src/main/resources/reference.conf
caffeine.jcache {
  # A named cache is configured by nesting a new definition under the caffeine.jcache namespace. The
  # per-cache configuration is overlaid on top of the default configuration.
  play-ws-cache {
    read-through {
      # If enabled, the entry is loaded automatically on a cache miss
      enabled = true
    }
    # The eviction policy for automatically removing entries from the cache
    policy {
      # The expiration threshold before lazily evicting an entry. This single threshold is reset on
      # every operation where a duration is specified. As expected by the specification, if an entry
      # expires but is not accessed and no resource constraints force eviction, then the expired
      # entry remains in place.
      lazy-expiration {
        # The duration before a read of an entry is considered expired. If set to 0 then the entry
        # is considered immediately expired. May be a time duration, null to indicate no change, or
        # "eternal" to indicate no expiration.
        access = 5m
      }
      # The expiration thresholds before eagerly evicting an entry. These settings correspond to the
      # expiration supported natively by Caffeine where expired entries are collected during
      # maintenance operations.
      eager-expiration {
        # Specifies that each entry should be automatically removed from the cache once a fixed
        # duration has elapsed after the entry's creation, the most recent replacement of its value,
        # or its last read. Access time is reset by all cache read and write operation. This setting
        # cannot be combined with the variable configuration.
        after-access = 5m
      }
      # The maximum bounding of the cache based upon its logical size
      maximum {
        # The maximum number of entries that can be held by the cache. This setting cannot be
        # combined with the weight configuration.
        size = 10000
      }
    }
  }
}

[debug]-restclient.baserestClient-使用url http://localhost:9001/entities/v2/867386732[trace]-p.a.l.w.ahc.standaloneahCwsclient@65b0b233)执行GET 1/Entities/v2/867386732[debug]-P.A.L.W.A.C.CachingAsynchTtpClient-Execute GET http://localhost:9001/Entities/v2/867386732:results=List（ResponseEntry（CacheableResponse（status=CacheableHttpResponseStatus（code=200，text=OK),headers=defaultHttpHeaders）[referrer-policy：origin-when-cross-origin,,2020年10月1日17:44:08格林威治时间，内容类型：application/json,内容长度:2144]，bodyParts size=1),GET,Map（）,Some(2020-10-02T10:44:08.760450-07:00[America/los_Angeles]))[trace]-C.T.C.ResponseElectionCalculator-FindMatchingResponse:request(http://localhost:9001/entities/v2/867386732,GET,TreeMap())，responses=List（StoredResponse(http://localhost:9001/entities/v2/867386732,200，TreeMap(date->List（Thu,内容-长度->列表(2144)，引用者-策略->列表（起源-当-交叉-起源，严格-起源-当-交叉-起源），x-框架-选项->列表（拒绝），x-xss-保护->列表（1；mode=block),X-Content-Type-Options->List（nosniff）,x-apport-cross-domain-policies->List（仅限master-only）,GET,Map())[debug]-p.a.l.w.a.c.cachingAsynchttpClient-execute GET http://localhost:9001/entities/v2/867386732：从cache中选择：ResponseEntry（CacheableResponse（status=CacheableHttpResponseStatus（code=200,text=OK）,mode=block,x-content-type-options：nosniff,x-apport-cross-domain-policies：master-only,Date：Thu,2020年10月1日17:44:08 GMT,Content-Type：application/json,Content-Length：2144,bodyParts size=1）,GET,Map（）,Some(2020-10-02t10:44:08.760450-07:00[America/los_Angeles])[trace]-c.t.c.currentage（headers：TreeMap（Date rer-policy->列表（起源-当-交叉-起源，严格-起源-当-交叉-起源），X-Frame-Options->列表（拒绝），x-xss-保护->列表（1；mode=block)，x-content-type-options->List（nosniff），x-approved-cross-domain-policies->List（仅限master-only))，现在:2020-10-01t17:44:38.690992z[GMT]，requesttime:2020-10-01t17:44:38.690274z[GMT]，responsetime:2020-10-01t17:44:38.690981z[GMT])[trace]-c.t.currentageCalculator

null

[debug]-P.S.A.O.A.Netty.Handler.HttpHandler-

请求DefaultFullHttpRequest（decoderesult:success，版本:http/1.1，内容:EmptyByteBufBE)GET/entities/v2/867386732 http/1.1主机:localhost:9001 accept://user-agent:ahc/2.1

响应DefaultHttpResponse（decoderesult：success,version:http/1.1)http/1.1200 OK referrer-policy:origin-when-cross-origin，strict-origin-when-cross-origin，X-Frame-Options：DENY X-XSS-Protection:1；mode=block x-content-type-options：nosniff x-允许-跨域-policies：master-only date：Thu,2020年10月1日17:44:38 GMT content-type：application/JSON content-length：2144

[debug]-P.S.A.O.A.N.channel.ChannelManager-为通道[ID:0x1FAC35F7,L:/127.0.0.1:49899]添加密钥:http://localhost:9001

null

Answer 1

我真的找到了它的工作原理。缓存不应该像Redis或Memcached这样管理单独的服务那样管理生存期，而是像浏览器那样工作，由HTTP响应中的头部管理。这里:https://github.com/playframework/cachecontrol/blob/e4694aa0665e2ccc5030ae1cf1d0b15ad5b98471/src/main/scala/com/typesafe/play/cachecontrol/freshnesscalculator.scala#l42

因此，我的解决方案是更改服务器，使其提供正确的头:cache-control“max-age=3600,public”