Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
HTTP response caching for Koa. Caches the response based on any arbitrary store you'd like.
app.use(require('koa-cash')({
// some options
}))
app.use(async (ctx, next) => {
// this response is already cashed if `true` is returned,
// so this middleware will automatically serve this response from cache
if (await ctx.cashed()) return
// set the response body here,
// and the upstream middleware will automatically cache it
ctx.response.body = 'hello world!'
})
Options are:
maxAge
Default max age (in milliseconds) for the cache if not set via await ctx.cashed(maxAge)
.
threshold
Minimum byte size to compress response bodies. Default 1kb
.
hash()
A hashing function. By default, it's:
function hash(ctx) {
return ctx.request.url
}
ctx
is the Koa context. By default, it caches based on the URL.
get()
Get a value from a store. Can be a regular function or an async
function,
which returns the cache's value, if any.
async function get(key, maxAge) {
return <cached-value>
}
Note that all the maxAge
stuff must be handled by you.
This module makes no opinion about it.
set()
Set a value to a store. Can be a regular function or an async
function.
async function set(key, value, maxAge) {
...
}
Note: maxAge
is set by .cash={ maxAge }
.
If it's not set, then maxAge
will be 0
, which you should then ignore.
Using a library like lru-cache, though this would not quite work since it doesn't allow per-key expiration times.
var cache = require('lru-cache')({
maxAge: 30000 // global max age
})
app.use(require('koa-cash')({
get (key, maxAge) {
return cache.get(key)
},
set (key, value) {
cache.set(key, value)
}
}))
This is how you enable a route to be cached.
If you don't call await ctx.cashed()
,
then this route will not be cached nor will it attempt to serve the request from the cache.
maxAge
is the max age passed to get()
.
If cached
is true
,
then the current request has been served from cache and you should early return
.
Otherwise, continue setting ctx.response.body=
and this will cache the response.
GET
and HEAD
requests are cached.200
responses are cached.
Don't set 304
status codes on these routes - this middleware will handle it for youDate
objects as well as Buffer
objects.
Otherwise, you may have to serialize/deserialize yourself.FAQs
HTTP response caching for Koa. HTTP response caching for Koa. Supports Redis, in-memory store, and more!
The npm package koa-cash receives a total of 1,115 weekly downloads. As such, koa-cash popularity was classified as popular.
We found that koa-cash demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.