Hello Maxim!
Thanks for the replay.
I will patch our service to support this temporary way.
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Fri, Sep 28, 2018 at 04:56:10AM -0400, Alex Zhang wrote:
> It seems that OpenSSL has changed the way TLSv1.3 cipher suites are
> configured.
> According to the document
> https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_cipher_list.html, the
> function SSL_CTX_set_cipher_list isn’
> how do I do it eaxtly regardless if it is cumbersome?.
Well you configure each individual nginx to listen (
https://nginx.org/en/docs/http/ngx_http_core_module.html#listen ) on a unix
socket:
Config on nginx1:
..
events { }
http {
server {
listen unix:/some/path/user1.sock;
..
}
Hoi Reinis,
I aswered inline and applied colors for my (#6633ff) and your (#cc9933) text
for better readability
Thanks a lot for your input
> I have a Synology NAS what runs a nginx as default web server to run all
their apps. I would like to extend it to meet the following. > > The
purposes
It’s fixed. Thank you
> On Sep 28, 2018, at 11:48 AM, Bee.Lists wrote:
>
> I often clear the cache and restart nginx.
Cheers, Bee
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Am 28.09.18 um 10:56 schrieb Alex Zhang:
> It seems that OpenSSL has changed the way TLSv1.3 cipher suites are
> configured.
> According to the document
> https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_cipher_list.html, the
> function SSL_CTX_set_cipher_list isn’t suitable for TLSv1.3
I often clear the cache and restart nginx.
> On Sep 28, 2018, at 11:19 AM, Reinis Rozitis wrote:
>
> If you are testing just with a browser make sure you've cleaned the cache (or
> disable it, or use some other tools which don't have cache (like wget for
> example)).
>
> If by chance you op
Hi,
On Thu, Sep 27, 2018 at 07:55:40PM +0300, Roman Arutyunyan wrote:
> Hi,
>
> On Thu, Sep 27, 2018 at 02:51:25PM +0200, Marcin Wanat wrote:
> > Hi,
> >
> > i am using latest (1.15.4) nginx with stream module.
> >
> > I am trying to create config with one primary server that will accept no
>
> First domain redirects port 80 to ssl 443.
> Second domain is just port 80.
> Third domain is just port 80.
>
> Second domain isn’t showing up, pointing to first domain. Third domain is
> working. Why would this happen?
If you are testing just with a browser make sure you've cleaned the cache
I currently have a DNS proxy that I would like to sinkhole certain domains.
For various reasons, I don't want to this within a DNS server itself. Is
there any way within the stream module to retrieve the domain from the
question portion of the DNS request? I don't see any existing variables that
ca
I have a test server up with 3 domains.
First domain redirects port 80 to ssl 443.
Second domain is just port 80.
Third domain is just port 80.
Second domain isn’t showing up, pointing to first domain. Third domain is
working. Why would this happen?
nginx.conf:
# user
Hello!
It seems that OpenSSL has changed the way TLSv1.3 cipher suites are
configured.
According to the document
https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_cipher_list.html, the
function SSL_CTX_set_cipher_list isn’t suitable for TLSv1.3, instead,
SSL_CTX_set_ciphersuits should be use
12 matches
Mail list logo
