Thanks Maxim!
On Mon, Apr 16, 2018 at 9:20 AM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Apr 16, 2018 at 03:16:13AM -0500, Andrei wrote:
>
> > I have an odd upstream application (out of my control) which sometimes
> > responds with incomplete pages, and a 200 error.. This causes blank pages
> > t
Looks like OpenSSL 1.1.1 finally fixed this (
https://github.com/openssl/openssl/issues/4301) and added early callback
(new in OpenSSL 1.1.1), which allows the application to switch SSL_CTXes
*before* TLS version negotiation.
Hopefully nginx 1.15 milestone will be able to take advantage of this.
This topic has been discussed in the past. eg: 3 years ago @
http://mailman.nginx.org/pipermail/nginx/2014-November/045738.html and
nginx couldn't fix it due to OpenSSL.
Has anything changed since then, with newer versions of OpenSSL?
___
nginx mailing li
Thanks Maxim!
This is something interesting to know.
We had an outage last year when we had bunch of virtual hosts all with
listen a.b.c.d:443 ssl;
and someone added a new virtual host with
listen a.b.c.d:443;
and caused 443 no longer doing SSL.
Based on what you said, this should not happen. I n
Hello!
On Mon, Apr 16, 2018 at 08:13:42AM -0700, Frank Liu wrote:
> Does that mean nginx will read and combine listen options from
> all virtual hosts and use that to create listening socket?
Yes. You can configure something like this:
server {
listen 443 ssl;
...
}
s
Hello!
On Mon, Apr 16, 2018 at 11:04:16AM -0400, Peter Booth wrote:
> Does this imply that that different behavior *could* be achieved
> by first defining virtual IP addresses (additional private IPs
> defined at the OS) which were bound to same physical NIC, and
> then defining virtual hosts
Does that mean nginx will read and combine listen options from all virtual
hosts and use that to create listening socket?
> On Apr 16, 2018, at 8:04 AM, Peter Booth wrote:
>
> Does this imply that that different behavior *could* be achieved by first
> defining virtual IP addresses (additional
Does this imply that that different behavior *could* be achieved by first
defining virtual IP addresses (additional private IPs defined at the OS) which
were bound to same physical NIC, and then defining virtual hosts that reference
the different VIPs, in a similar fashion to how someone might c
Hello!
On Mon, Apr 16, 2018 at 03:16:13AM -0500, Andrei wrote:
> I have an odd upstream application (out of my control) which sometimes
> responds with incomplete pages, and a 200 error.. This causes blank pages
> to appear in cache. Is there a way to exclude from/bypass cache if the
> content-le
Hello!
On Mon, Apr 16, 2018 at 07:26:11AM +, Frank Liu wrote:
> Can I use different listen parameters for virtual hosts using the same
> port? Eg, one vh has “listen 443 ssl;” and the other one has “listen 443
> ssl h2;”
No. Options like "ssl" and "h2" can be repeated multiple times to
mak
Hello!
On Sun, Apr 15, 2018 at 07:01:42PM +0200, Ondrej Jombik wrote:
> On Fri, 13 Apr 2018, Maxim Dounin wrote:
>
> >> As you can see in my example, I am not even using or calling test_fnc()
> >> yet. But Perl code simply fails on startup with this error message:
> >>
> >> -- Unit nginx.service
It's possible if the so-called 'virtual machines' of yours are NOT on the
same machine
On Mon, 16 Apr 2018 10:19 A. Schulze, wrote:
>
> Frank Liu:
>
> > Can I use different listen parameters for virtual hosts using the same
> > port? Eg, one vh has “listen 443 ssl;” and the other one has “listen
Frank Liu:
Can I use different listen parameters for virtual hosts using the same
port? Eg, one vh has “listen 443 ssl;” and the other one has “listen 443
ssl h2;”
no, that's impossible (I think...)
https://nginx.org/r/listen
...
The listen directive can have several additional parameters sp
Hello!
I have an odd upstream application (out of my control) which sometimes
responds with incomplete pages, and a 200 error.. This causes blank pages
to appear in cache. Is there a way to exclude from/bypass cache if the
content-length header from the upstream is lower than 5kb for example?
Than
Can I use different listen parameters for virtual hosts using the same
port? Eg, one vh has “listen 443 ssl;” and the other one has “listen 443
ssl h2;”
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
15 matches
Mail list logo