cucumber-ltd / eu Goto Github PK

I'm not sure if you're tracking new cache stores anywhere, so this might just be a quick FYI.

I've been maintaining a pure JavaScript persistent key-value storage library named Medea.

I built the eu-medea-store module to marry Eu with Medea.

So... if you need a legit (not in-memory) cache store that is persistent, requires no native modules, and runs in-process.... here you go!

Atm previously cached reponses gets returned if the server responds with 304, great 👍 Although as the cached response expiry isnt extended, all subsequent requests will still perform requests against the server.

Any thoughts on extending the cachedResponse.expiryTimeMillis on 304 responses, increasing the possibility of hitting the cache immediately instead of requesting the server?

According to the HTTP spec, a 302 response is

cacheable if indicated by a Cache-Control or Expires header field.

Even if we changed the logic in eu, request() won't emit 302 responses unless it's passed {followRedirect: false}

Can we make eu cache 302 responses without users having to implement redirection themselves? What would be the best approach?