Re: enable reuseport then only one worker is working?

2016-03-01 Thread drhowarddrfine
After a brief search, I was correct, and there are technical reasons for not doing this and Linux and Dragonfly are doing it wrong. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,264913,264964#msg-264964 ___ nginx mailing list nginx@nginx.or

Re: enable reuseport then only one worker is working?

2016-03-01 Thread drhowarddrfine
Yes but is there a technical reason why it hasn't been done yet? Does FreeBSD have a reason to not do it? Just because Linux did does not mean it should be done. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,264913,264961#msg-264961 ___ ngi

Re: enable reuseport then only one worker is working?

2016-03-01 Thread drhowarddrfine
Do you know why FreeBSD does not do this? Is there a technical reason to not do that? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,264913,264959#msg-264959 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/ng

Re: Server 1 redirects, Server 2 does not

2015-08-20 Thread drhowarddrfine
Doing a curl -I -L http://www.site1.com/ returns this: HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 21 Aug 2015 03:04:50 GMT Content-Type: text/html Content-Length: 178 Connection: keep-alive Location: https://site1.com/ HTTP/1.1 200 OK Server: nginx Date: Fri, 21 Aug 2015 03:04:50 GMT

Re: Server 1 redirects, Server 2 does not

2015-08-20 Thread drhowarddrfine
Note that I upgraded the server so I could turn httpv2 on. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261156,261157#msg-261157 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Server 1 redirects, Server 2 does not

2015-08-20 Thread drhowarddrfine
This problem may have been around before I updated to nginx version 1.9.4 but I'm not sure. I have one VPS with two IP addresses. Server 1 redirects port 80 www and non-www to port 443 requests along with www requests on port 443 to the non-www web site. iow, http://(www.)site1.com/ and https://w

Removing blank location block causes 404 errors

2014-03-20 Thread drhowarddrfine
I was just typing what I think may be the reason. That other location blocks may be picking this up and eventually returning a 404 but, with that block in there, the image and css requests are getting "handled", ie, nothing is done to them at all, and then retrieved from their proper director

Removing blank location block causes 404 errors

2014-03-20 Thread drhowarddrfine
I'm new to nginx and had this in my conf file which I had copied some time ago but never filled it in and continued building a test page with images, css and javascript: location ~* ^.+\.(css|js|jpg|jpeg|gif|png|ico|gz|svg|svgz|ttf|otf|woff|eot|mp4|ogg|ogv|webm|pdf)$ { } Today, I deleted