It is fairly simple to hack nginx and use Lua to reload the cache timed or
via a request.
The code is already there, its just a matter of calling it again.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,281179,281225#msg-281225
___
nginx mai
One more approach is to not change the contents of resources without also
changing their name. One example would be the cache_key feature in Rails, where
resources have a path based on some ID and their updated_at value. Whenever you
modify a resource it automatically expires.
Sent from my iPho
> How does one ensure cache consistency on all edges?
I wouldn't - you can never really rely on anything being consistent cached,
there will always be stuff that doesn't follow the standards and thus can give
an inconsistent state for one or more users.
What I'd do, would simply to be to purge
Hi Lucas,
Thank you for this. GEM all over. I didn’t know curl had –resolve.
This is a more a generic question: How does one ensure cache consistency on
all edges? Do people resort to a combination of expiry + background update
+ stale responding? What if one edge and the origin was updated t
Hi,
Are the any plans to add this feature?
If one has less software to run stuff, and if hitch can be avoided in some use
cases, I think that would be a plus.
Thanks for you answer.
Best Regards,
Danila
> On 13 Sep 2018, at 21:42, Maxim Dounin wrote:
>
> Hello!
>
> On Thu, Sep 13, 2018 at 0
Hello!
On Thu, Sep 13, 2018 at 09:26:31PM +0300, Danila Vershinin wrote:
> Hello,
>
> I’m trying to basically use nginx as replacement to hitch (for Varnish).
>
> Request goes like this: browser → nginx (stream SSL) → varnish (HTTP2 on) →
> backend HTTP
>
> stream {
> server {
> lis
Hello,
I’m trying to basically use nginx as replacement to hitch (for Varnish).
Request goes like this: browser → nginx (stream SSL) → varnish (HTTP2 on) →
backend HTTP
stream {
server {
listen 443 ssl;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
Hello!
On Wed, Sep 12, 2018 at 12:41:15PM -0700, Quintin Par wrote:
> Not to sounds demanding, but do you have any examples (code) of proxy_store
> bring used as a CDN. What’s most important to me in the initial cache
> warming. I should be able to start a new machine with 30 GB of cache vs. a
>
