After a brief search, I was correct, and there are technical reasons for not doing this and Linux and Dragonfly are doing it wrong.by drhowarddrfine - Nginx Mailing List - English
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.by drhowarddrfine - Nginx Mailing List - English
Do you know why FreeBSD does not do this? Is there a technical reason to not do that?by drhowarddrfine - Nginx Mailing List - English
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 Content-Type: text/html; charset=utf-8 Now I'm really confused. Using Chrome on my dby drhowarddrfine - Nginx Mailing List - English
Note that I upgraded the server so I could turn httpv2 on.by drhowarddrfine - Nginx Mailing List - English
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://www.site1.com/ properly get 301 redirected to https:site1.com/ Site 2 does not do this and only rby drhowarddrfine - Nginx Mailing List - English
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 directory path. _______________________________________________ nginx mailing list nginx@nginx.org htby drhowarddrfine - Nginx Mailing List - English
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 that block and now the images, css and javascript files are all returned a 404. I don't understand what'by drhowarddrfine - Nginx Mailing List - English
I know there's something fundamental I'm doing wrong but I'm thisclose getting nginx to work for me. I have the typical set up where I want any requests to a directory, such as 'mysite.com/pages' be served by 'index.html' and any requests for '/pages/page1' to be served by page1.html. I set up a directory called '/test' which is sent to a thttpd set up that serves a cgi generated page and this woby drhowarddrfine - How to...
![]() |
![]() |
![]() |
![]() |
|