Is RequestHeader.cookies API changed intentionally (2.5 vs 2.6)?

Play Framework
1

We’re using Silhouette project and trying to migrate from Play2.5/Scala 2.11 to Play2.6.15/Scala 2.12.6
And it seems like there is some issue around RequestHeader.cookies API. Silhouette CookieAuthenticatorService contains following code:

      request.cookies.get(settings.cookieName) match {
        case Some(cookie) => ....
        case None => Future.successful(None)

In Play 2.5 request.cookies never throws exception and returns Cookies backed by empty Map. In Play 2.6, it tries to do TypedMap.apply(key) and throws NoSuchElementException:

Caused by: java.util.NoSuchElementException: key not found: Cookies
	at scala.collection.immutable.Map$Map3.apply(Map.scala:167)
	at play.api.libs.typedmap.DefaultTypedMap.apply(TypedMap.scala:92)
	at play.api.mvc.RequestHeader.cookies(RequestHeader.scala:221)
	at play.api.mvc.RequestHeader.cookies$(RequestHeader.scala:221)
	at play.api.mvc.WrappedRequest.cookies(WrappedRequest.scala:16)
	at com.mohiva.play.silhouette.impl.authenticators.CookieAuthenticatorService.$anonfun$retrieve$2(CookieAuthenticator.scala:210)
	at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:303)
	at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37)

Seems like vanilla Play2.6 always initiates RequestAttrKey.Cookies attribute (in DefaultRequestFactory), and it somehow lost in my integration with Silhouette or/and FakeRequest (an exception is thrown in tests), but I would like to know, is that change looking like breaking backward-compatibility, isn’t it?

2

Same here. I’m using Play 2.7.3

java.util.NoSuchElementException: key not found: Cookies
        at scala.collection.immutable.Map$Map1.apply(Map.scala:114)
        at play.api.libs.typedmap.DefaultTypedMap.apply(TypedMap.scala:103)
        at play.api.mvc.RequestHeader.cookies(RequestHeader.scala:230)
        at play.api.mvc.RequestHeader.cookies$(RequestHeader.scala:230)
        at play.api.mvc.RequestHeaderImpl.cookies(RequestHeader.scala:357)
        at play.api.i18n.DefaultMessagesApi.preferred(Messages.scala:500)
        at play.api.i18n.I18nSupport.request2Messages(I18nSupport.scala:33)
        at play.api.i18n.I18nSupport.request2Messages$(I18nSupport.scala:33)
3

Is it possible to recreate a reproducer? Is this happening only when using Play + Silhouette or a vanilla Play application also presents the same problem?

4

Is it possible to recreate a reproducer?

No, it isn’t intentionally.

However, we often get the error every day.
I don’t think it’s going to affect our users directly.

Is this happening only when using Play + Silhouette or a vanilla Play application also presents the same problem?

Our project doesn’t use Silhouette. So, a vanilla Play application.