Am I missing this: "If a server is the only server for a listen port, then nginx will not test server names at all (and will not build the hash tables for the listen port). However, there is one exception. If a server name is a regular expression with captures, then nginx has to execute the expression to get the captures." http://nginx.org/en/docs/http/server_names.htmlby tcbarrett - Nginx Mailing List - English
Does having a listen directive in a server block over ride blocks without? I have a slightly complex set up, proxying traffic depending on url to various other machines on the network. Something a bit like this: http://pastebin.com/MSAFJKLV The middle block hogs all the traffic, and all requests are sent to mysssl.example.com. What am I missing?by tcbarrett - Nginx Mailing List - English
I'm thinking of setting up multiple server blocks with the same document root (all one WP mutisite), rather than one server block with a long list of aliases in the server_name. Trivial set up would be that they are all identical, except for the server_name directive. Is this a bad idea? Does it matter?by tcbarrett - Nginx Mailing List - English
kaspars Wrote: ------------------------------------------------------- > Well, if you set cache to expire 30 years from now > the browser should honor that, that is if no > Last-Modified is set. I have it set to 30m (30 minutes, right?). If I update, for example, some css files and then a do a hard refresh on a) a Mac then I get the new css or b) Windows 7 then I keep getting the cby tcbarrett - Nginx Mailing List - English
Nobody has any ideas?by tcbarrett - Nginx Mailing List - English
Hi Loving nginx, thanks Igor! I'm caching static files in a very traditional way, I hope: location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ { #expires max; expires 30m; access_log off; log_not_found on; } I would like to have longer caching. Sometimes there is a fast turn around on live sites and clients have an issue bursting the cache. These tend to bby tcbarrett - Nginx Mailing List - English