Re: nginx configuration with self signed certificates - getting error

2015-12-28 Thread sumeetmaru
Please if anyone could take a look and reply? Thanks Posted at Nginx Forum: https://forum.nginx.org/read.php?2,263695,263727#msg-263727 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Building nginx from Source on Windows

2015-12-28 Thread Maxim Dounin
Hello! On Mon, Dec 28, 2015 at 11:44:32AM -0800, Igal @ Lucee.org wrote: > Thank you, Maxim! > > I prefer to build with gcc if that is possible. MS Visual C is a mess IMO. > As a Java developer I'm used to more intuitive tools and options, I guess. > > I will try to add --with-select_module an

Re: Building nginx from Source on Windows

2015-12-28 Thread Igal @ Lucee.org
Thank you, Maxim! I prefer to build with gcc if that is possible. MS Visual C is a mess IMO. As a Java developer I'm used to more intuitive tools and options, I guess. I will try to add --with-select_module and hopefully that will do the trick. I will report back once I have some findings

Reverse Proxy File Upload Failure

2015-12-28 Thread Nicholas J Ingrassellino
I am running Nginx v1.8.0 to serve all my static files and node.js to do the dynamic stuff. One of the things Nginx needs to do is proxy files over to node.js which stores the file. node.js seems to get ~26K of the file and then nothing (not even sure the connection closes when the data "finish

Re: SSI URI path decoding/encoding issue

2015-12-28 Thread Maxim Dounin
Hello! On Thu, Dec 24, 2015 at 11:20:04PM +0100, Martin Grotzke wrote: > we experienced an issue with SSIs (include virtual): nginx at first decodes > the URI path and encodes it before passing the request to the upstream. If > an URI path segment contains %2F (encoded slash), the decoded slash i

Re: Building nginx from Source on Windows

2015-12-28 Thread Maxim Dounin
Hello! On Sun, Dec 27, 2015 at 11:44:16AM -0800, Igal @ Lucee.org wrote: > update: so I ran the following command: > > auto/configure --with-cc=gcc --prefix= --conf-path=conf/nginx.conf > --pid-path=nginx.pid --http-log-path=logs/access.log > --error-log-path=logs/error.log--without-http_gzip_m

Re: Nginx catching all domains without wildcard

2015-12-28 Thread B.R.
In the configuration you provided, there are 3 server blocks: - 80 www.domain.com - 443 (default server) domain.com - 127.0.0.1:8081 elsitar.com There is no server block defined for uk.domain.com (you main config file has an include directive for a /etc/nginx/uk.domain.com file which is commented