> If you nevertheless observe 500 being returned in practice, this might be the
> actual thing to focus on.
Even with sub 100 requests and 4 workers, I've experienced it multiple times,
where simply because the number of cache keys got exceeded, it was throwing 500
internal server errors for ne
Hello!
On Mon, May 17, 2021 at 07:33:43PM +, Lucas Rolff wrote:
> Hi Maxim!
>
> > - The attack you are considering is not about "poisoning". At
> > most, it can be used to make the cache less efficient.
>
> Poisoning is probably the wrong word indeed, and since nginx
> doesn't really han
Hi Maxim!
> - The attack you are considering is not about "poisoning". At most, it can
> be used to make the cache less efficient.
Poisoning is probably the wrong word indeed, and since nginx doesn't really
handle reaching the limit of keys_zone, it simply starts to return a 500
internal serv
Hello!
On Mon, May 17, 2021 at 02:47:33PM +, Lucas Rolff wrote:
> Hi Maxim,
>
> Thanks a lot for your reply!
>
> I'm indeed aware of the ~8k keys per mb of memory, I was just
> wondering if it was handled differently when min_uses are in
> use, but it does indeed make sense that nginx has
Hi Maxim,
Thanks a lot for your reply!
I'm indeed aware of the ~8k keys per mb of memory, I was just wondering if it
was handled differently when min_uses are in use, but it does indeed make sense
that nginx has to keep track of it somehow, and the keys zone makes the most
sense!
> Much like
Hello!
On Sun, May 16, 2021 at 04:46:17PM +, Lucas Rolff wrote:
> Hi everyone,
>
> I have a few questions regarding proxy_cache and the use of
> proxy_cache_min_uses in nginx:
>
> Let’s assume you have an nginx server with proxy_cache enabled,
> and you’ve set proxy_cache_min_uses to 5;
>
Hi everyone,
I have a few questions regarding proxy_cache and the use of
proxy_cache_min_uses in nginx:
Let’s assume you have an nginx server with proxy_cache enabled, and you’ve set
proxy_cache_min_uses to 5;
Q1: How does nginx internally keep track of the count for min_uses? Is it using
SHM
