On 2016-09-14 02:02, c0nw0nk wrote: > I take it the module is a part of the Nginx.exe build and not > Nginx_basic.exe The fact that nginx comes with the module, and that it is available at build-time, does not mean it's built along. Parameter --with-http_realip_module must be passed to configure, at least. Not sure how it is for these builds, can't test them. Doesn't nginx_basic.exe supporby FinalX - Nginx Mailing List - English
On 2016-08-23 15:31, Maxim Konovalov wrote: > Let me repeat: nginx.org supports HTTPS. > I don't think it adds any measurable security here but it's matter > of religion but you can use it for free if you think it does. +1 Although it would be chique if nginx.org would advertise a HSTS-header so that next requests are over HTTPS if a browser supports it. You could also opt to add it toby FinalX - Nginx Mailing List - English
Hi Charles, IPv6 listeners can also accept IPv4 requests. This will result in IPs being passed through to logs and such like ::ffff:192.168.123.101. If you do not want this and do want both, add ipv6only=on to the IPv6 listen line. Daniƫl On Jul 26, 2016 02:25, "Charles Lawrence" <geuis.teses@gmail.com> wrote: > I'm in the process of setting up a new server built on ubuntuby FinalX - Nginx Mailing List - English
On 2016-06-23 09:39, Moritz Machner wrote: > Hello, > > is it possible to dynamical get an cert/key from an database or an > script for SNI? > > I want to dynamical add new domains with certs for an web app without > changing the config oder restarting nginx: > > 1. get SNI request for domain example342343.com > http://example342343.com > 2. ask mysql for the ceby FinalX - Nginx Mailing List - English
Hi Maddy, Op 4-2-2016 om 13:31 schreef smsmaddy1981: > ./nginx > nginx: bind() to 0.0.0.0:80 failed (13: Permission denied) You edited the sudoers file to allow gvp to run programs as root. In order to do so, you have to put "sudo" in front of the command, which stands for "do as super user". In this case, your line would've been instead: sudo ./nginx As a side-notby FinalX - Nginx Mailing List - English
Hi! I'm running an HTTP-based application (Plex) that decides whether or not to use SSL based on what the client decides to talk to it. I would like to be able to control what it does and who's able to connect to it a bit more, and I'd like to do that with nginx. I've tried disabling all SSL, which works, but then the frontend client that's loaded over SSL will obviously get mixed content probleby FinalX - Nginx Mailing List - English
If you're using a 1-config-per-site setup, then yes, you could. It completely depends on your setup as to where you need to place it. You can put it in any existing file that already has a server directive in there. Just make sure none of the other server configs/files have the default_server in their listen directive. The server name of _ just makes sure it won't conflict with any existing nameby FinalX - Nginx Mailing List - English
You could use an extra host config with a default_server, like so: server { listen 80 default_server; server_name _; return 444; } You can find this example on http://nginx.org/en/docs/http/server_names.htmlby FinalX - Nginx Mailing List - English