Hello!
On Sat, May 08, 2021 at 09:16:39PM +0300, Reinis Rozitis wrote:
> > Thanks for the report, it looks like this change broke things:
> >
> > changeset: 7738:554c6ae25ffc
> >
> > The only fix I can think of is to rewrite the lingering close so it will
> happen after the request is logged.
> Thanks for the report, it looks like this change broke things:
>
> changeset: 7738:554c6ae25ffc
>
> The only fix I can think of is to rewrite the lingering close so it will
happen after the request is logged.
Thkx Maxim for finding the cause.
I suppose that this is considered a bug then? If
Hello!
On Sat, May 08, 2021 at 07:33:07PM +0300, Reinis Rozitis wrote:
> Hello.
> I have a strange issue where for a POST request having any form data Nginx
> after version 1.9.4 doesn't log $ssl_protocol (or any other $ssl_*)
> variable.
>
>
> I have a configured custom accesslog:
>
> log_for
Hello.
I have a strange issue where for a POST request having any form data Nginx
after version 1.9.4 doesn't log $ssl_protocol (or any other $ssl_*)
variable.
I have a configured custom accesslog:
log_format main '... $ssl_protocol $ssl_cipher $server_port';
A simple script ( for example from
Thanks Maxim for further explaining!
We do listen to a huge number of IPs with tons of traffic and huge spikes
on them. We really need to avoid any type
of congestion, therefore the reuseport.
While many of the ip:port combos are simply there for failover purposes and
actually aren't "in use", I
