Hello,
how do I best handle multiple locations that use the same code block? I do not
want to repeat the { … } part. Is there a way to do this with logical or
between regular expressions?
The first variation is that sometimes there are query parameters, and sometimes
there are not. The second
Maxim Dounin Wrote:
---
> Hello!
>
> On Fri, Nov 23, 2018 at 01:05:55PM -0500, Olaf van der Spek wrote:
>
> > What's the recommendation for distros? Should they explicitly enable
> > TLSv1.3?
> > Ideally they'd just stick to upstream defaults, h
Hello!
On Fri, Nov 23, 2018 at 01:05:55PM -0500, Olaf van der Spek wrote:
> What's the recommendation for distros? Should they explicitly enable
> TLSv1.3?
> Ideally they'd just stick to upstream defaults, hence my question about the
> default.
The recommendation for distros is to don't mess wit
What's the recommendation for distros? Should they explicitly enable
TLSv1.3?
Ideally they'd just stick to upstream defaults, hence my question about the
default.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,282098,282108#msg-282108
___
ng
Hello!
On Fri, Nov 23, 2018 at 04:33:33PM +0100, Jack Henschel wrote:
> On 11/23/18 3:11 PM, Maxim Dounin wrote:
> > Hello!
> >
> > On Fri, Nov 23, 2018 at 09:23:01AM +0100, Jack Henschel wrote:
> >
> >> Hi Maxim,
> >>
> >> thanks for the quick confirmation!
> >>
> >>> The Host header is set to
Hello!
On Fri, Nov 23, 2018 at 08:43:03AM -0500, Olaf van der Spek wrote:
> Hi,
>
> Why isn't 1.3 enabled by default (when available)?
>
> Syntax: ssl_protocols [SSLv2] [SSLv3] [TLSv1] [TLSv1.1] [TLSv1.2]
> [TLSv1.3];
> Default:
> ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
>
> http://ngi
On 11/23/18 3:11 PM, Maxim Dounin wrote:
> Hello!
>
> On Fri, Nov 23, 2018 at 09:23:01AM +0100, Jack Henschel wrote:
>
>> Hi Maxim,
>>
>> thanks for the quick confirmation!
>>
>>> The Host header is set to what you wrote in the "proxy_pass"
>>> by default. That is, it will be "backend" with th
Closing the connection wouldn't really solve the issue would it?
There has to be a better way to solve this.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,282096,282104#msg-282104
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx
> Why do you want to do this?
In a cluster of many nginx servers we had one faulty node that was
delivering only errors. In that special case a default vhost replied an
"domain not configured" error, because the underlying configuration was
inaccessible. The health check was not firing, because su
Hello!
On Fri, Nov 23, 2018 at 09:23:01AM +0100, Jack Henschel wrote:
> Hi Maxim,
>
> thanks for the quick confirmation!
>
> > The Host header is set to what you wrote in the "proxy_pass"
> > by default. That is, it will be "backend" with the above
> > configuration.
>
> Wouldn't it make m
Why do you want to do this?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,282096,282099#msg-282099
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
Why isn't 1.3 enabled by default (when available)?
Syntax: ssl_protocols [SSLv2] [SSLv3] [TLSv1] [TLSv1.1] [TLSv1.2]
[TLSv1.3];
Default:
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_protocols
Posted at Nginx Forum:
https://forum.ng
Hello,
we use NGINX as http/2 and TLS offloader. Therefore it is responsible for
connection handling. (Most of the requests are proxy_pass'ed to upstream
servers. However, some few requests are served from local files.)
Now, I would like to close the client connection under certain
circumstances.
Hi Maxim,
thanks for the quick confirmation!
> The Host header is set to what you wrote in the "proxy_pass" by default.
> That is, it will be "backend" with the above configuration.
Wouldn't it make more sense to use the hostname from the particular upstream
server?
I see two scenarios where
14 matches
Mail list logo
