Maxim Dounin Wrote:
---
> Multiple cache files for the same key can be created if a backend
> response uses the Vary mechanism to allow multiple resource
> variants. It is supported and taken into account when caching
> since nginx 1.7.7, http
Hi.
Am 19-11-2015 14:40, schrieb Valentin V. Bartenev:
On Thursday 19 November 2015 11:56:37 B.R. wrote:
Aleks: Have you even read the 1st message from lakarjail?
Well a little bit.
(s)he said he had a look at it. It seems (s)he only wants
interactive
solutions with the password being w
Hello!
On Thu, Nov 19, 2015 at 12:12:18PM -0200, Guilherme wrote:
> In these cases, when Vary is present in response headers and generate
> multiple cache files for the same key, how nginx determines cache file
> names for variants?
Secondary keys are calculated as an MD5 hash of the main key a
Hi
On Thu, Nov 19, 2015, at 10:40 PM, Valentin V. Bartenev wrote:
> "named pipe can also be used instead of a file" - doesn't that help to
> make
> interactive solution?
>
Considering the admin must be ready when the "service" starts, I'm
wondering the benefit of using systemd or other service m
Maxim,
In these cases, when Vary is present in response headers and generate
multiple cache files for the same key, how nginx determines cache file
names for variants?
Tks,
Guilherme
On Thu, Nov 19, 2015 at 11:26 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Nov 18, 2015 at 09:40:45PM -0500
On Thursday 19 November 2015 11:56:37 B.R. wrote:
> Aleks: Have you even read the 1st message from lakarjail?
>
> (s)he said he had a look at it. It seems (s)he only wants interactive
> solutions with the password being written nowhere.
> Although the reasoning appearing strange to me (someone n
Hello!
On Wed, Nov 18, 2015 at 09:40:45PM -0500, semseoymas wrote:
> First, the specs:
> nginx version: nginx/1.8.0
[...]
> The problem here: if people asks nginx for the same request_uri, it will
> create multiple files!! this way, the cache is not running ok...
Multiple cache files for the
Hello!
On Wed, Nov 18, 2015 at 10:36:07PM -0800, Frank Liu wrote:
> I understand nginx writes the log when request completes, but is time_local
> (or time_iso8601, msec) representing the time that the request was received
> or when the request completes and log written? I know Apache and AWS ELB
Aleks: Have you even read the 1st message from lakarjail?
(s)he said he had a look at it. It seems (s)he only wants interactive
solutions with the password being written nowhere.
Although the reasoning appearing strange to me (someone needs to be there
in case of unexpected reload/restart, other
