upcache
upcache copied to clipboard
Caching proxy dynamically configured by upstream applications
https://datatracker.ietf.org/doc/draft-ietf-httpbis-cache-groups/ Also: That would be the right header, and there is already a somewhat long list of directives https://developer.mozilla.org/fr/docs/Web/HTTP/Headers/Cache-Control Cache-Control: max-age=3600, tag=A;B;C, lock=permA;permB, map=/url, ...
The public key handshake protocol allow changing the rsa key as long as jwt peremption is less than the time between two renewals (to avoid having to deal with more...
https://httpwg.org/http-extensions/draft-ietf-httpbis-cache-header.html https://httptoolkit.tech/blog/status-targeted-caching-headers/
tag api should expose similar methods as lock api: - headers(res, list) - vary(array or list of arguments)
It just doesn't match how upcache tags are set w.r.t. express middlewares. It would be more useful to configure upcache.tag with some filter(name, req) function.
https://github.com/openresty/srcache-nginx-module#srcache_store_ranges this will be used notably by https://calibreapp.com/blog/2018-08-16-native-lazy-load/
There's no point in caching those.
When nginx will allow out of tree compilation, it will be easy to distribute separately a module that installs the right config and hooks into nginx instead of multiple conf...
First it protects upstream in case of several kinds of ddos, and second it improves performance in case of simultaneous requests. Idea for implementation in https://github.com/openresty/srcache-nginx-module/issues/53
It will be much easier to maintain "server" compatibility while changing client api.