This repository was archived by the owner on Jun 6, 2021. It is now read-only.
This repository was archived by the owner on Jun 6, 2021. It is now read-only.
Should not cache with invalid max-age freshness extension separator #69
Description
When the invalid max-age extension separate provided(for example max-age=1-100) it should not be cached. Current behavior is that it will throws exception.
java.lang.NullPointerException
at org.reaktivity.nukleus.http_cache.internal.proxy.cache.SurrogateControl.getSurrogateFreshnessExtension(SurrogateControl.java:51)
at org.reaktivity.nukleus.http_cache.internal.proxy.cache.SurrogateControl.getSurrogateFreshnessExtension(SurrogateControl.java:38)
at org.reaktivity.nukleus.http_cache.internal.stream.ProxyConnectReplyStream.handleCacheableRequest(ProxyConnectReplyStream.java:178)
at org.reaktivity.nukleus.http_cache.internal.stream.ProxyConnectReplyStream.handleBegin(ProxyConnectReplyStream.java:107)
at org.reaktivity.nukleus.http_cache.internal.stream.ProxyConnectReplyStream.beforeBegin(ProxyConnectReplyStream.java:77)
To reproduce the issue run EdgeArchProxyIT.shouldNotCacheWithInvalidMaxAgeFreshnessExtensionSeparator