bypass for errors about apicache HOT 7 CLOSED

it would be great if we could have an option to save in cache only responses with status 200, or add a handler function on the start configuration

from apicache.

See docs and/or Wiki for statusCode caching bypasses. This has been added!

from apicache.

@tomstrummer I'm about to document this feature now, but I've previously added a pseudo middleware "toggle" param to the existing middleware call. This toggle function has access to the req/res just before the cache pass - so it's the last possible chance to intercept and cancel the cache pass (by returning false). Because it has access to these shared resources, embed any flags you need into one of them and check from within the toggle function.

A quick example:

function noErrors(req, res) {
  return !res.customFailure;
}

app.get('/myroute', cache('1 hour', noErrors), function(req, res) {
  res.customFailure = true;
  res.send('ok!');  // this response will not be cached because noErrors() will return false;
});

Personally I use it to prevent caching on private/admin requests (which should never be stale). This way I can share a single API between public and private requests, and simply detect which type of request is coming through to route it (not not) to the cache layer.

That help I hope? If not, let me know and I'll try to help as best I can.

from apicache.

Hey that's great that you've already worked on this! Is this present in 0.0.12? If so, it's not working for me. What I'm seeing right now is my noErrors function being called before my request handler.

But if it does work the way you've described, I think it's acceptable. If I called res.status(500) in my route handler I can then check for res.statusCode < 400 in my cache control function. So it sounds like it would meet my needs.

from apicache.

You know, @tomstrummer, you're absolutely right... this toggle allows the cache bypass before the "work" gets done, not after (to prevent caching). I was using it to check headers, and outcomes/injections from previous middleware layers.

I'll take a look at it and see if I can refactor into a pattern that's more flexible.

from apicache.

👍

from apicache.

Will sort this when I return to the States (and reliable internet) in a few weeks! Thanks for the patience guys!

~
Kevin

On 02 Nov 2015, at 00:17, Aaron Ryden [email protected] wrote:

—
Reply to this email directly or view it on GitHub.

from apicache.