Congratulations on the release Igor! Could you please provide a brief description of the "loader_files", "loader_sleep", and "loader_threshold" directives so that they can be documented in the wiki?by Ensiferous - Nginx Mailing List - English
Hi! You need a third party module ( http://wiki.nginx.org/3rdPartyModules ) such as EY Balancer: http://github.com/ry/nginx-ey-balancer/tree/masterby Ensiferous - Nginx Mailing List - English
Hi, I think you have misunderstood the purpose of the proxy_cache_path. This is the path where you want the cached files to be saved to, not the path of the files to be cached. The files to be cached will come from your upstream you reach via proxy_pass. You cannot use proxy cache with static files. (Besides, your OS will handle caching frequently accessed files)by Ensiferous - Nginx Mailing List - English
There might also be a more specific location that takes precedence. Have read on the resources linked here: http://wiki.nginx.org/Quickstart to understand better how nginx work.by Ensiferous - Nginx Mailing List - English
You paste really doesn't contain anything interesting at all. Here's things that may help us help you: - Your entire config file - The output of nginx -V - A live website actually running on Nginx (doesn't have to be port 80)by Ensiferous - Nginx Mailing List - English
There is a server status module called stub status, but it's on a server wide level, not vhost. You have to parse the access logs if you want vhost granularity.by Ensiferous - Nginx Mailing List - English
Yeah it's a weird situation. As a user I would probably expect that the range applied to the actual content served, before it was compressed. So that if I request 100 bytes when everything is transferred and decompressed I have 100 bytes worth of content.by Ensiferous - Nginx Mailing List - English
Hi! A question was posed in IRC yesterday about Range requests not being honoured when using gzipping. After testing it I've confirmed that there appears to be a problem. I've put a test file online you can test against: http://216.218.189.55/range.txt The following curl runs were used to test: curl -r 0-5 http://216.218.189.55/range.txt <- gives 6 bytes curl -r 0-5 --compressed httby Ensiferous - Nginx Mailing List - English
Nginx does not cache anything by default. You browser does, though.by Ensiferous - How to...
The difference in the Nginx memory size can be due to the modules you have compiled in or the amount and size of buffers you have allocated. The difference in the PHP memory size can be anything from modules compiled in/dynamically linked to what type of scripts you're running. One thing I can tell you with certainty is that Nginx does not affect the memory usage of PHP.by Ensiferous - Nginx Mailing List - English
Make sure that your PHP output links to the https version of images and not the http version.by Ensiferous - Nginx Mailing List - English
Hi. The two are unrelated, Nginx has no effect on PHP as there is a fastcgi abstraction layer inbetween them. Recompiling Nginx does not recompile PHP.by Ensiferous - Nginx Mailing List - English
Hi, This directive just sets when to use direct IO and when not to, it does not affect the Nginx output buffers which are used when sendfile is turned off. Similarly, the cached value you see in free -m is the amount your OS use for caching IO, not nginx. If you wish to turn this off you must do so at the OS level.by Ensiferous - Nginx Mailing List - English
It used to be a Google search box and it worked even worse than it does now. As far as I know the search is currently handled via Sphinx so there's plenty of options for tuning it, for example I think it'd be a lot better if it was configured to do partial word matching on the title and give that more weight than the body. Experimentation should lead to much improved results. The biggest proby Ensiferous - Nginx Mailing List - English
Resumable downloads are just HTTP range requests and Nginx support this by default.by Ensiferous - Nginx Mailing List - English
Please elaborate on how allowing a filename like .dsadsada/sad.php is insecure.by Ensiferous - Nginx Mailing List - English
I'm curious, do you base that logical reason on a "the code should allow this" or "it would be nice to have"? There's really no way to use include in an upstream directive. You should make sure your vhosts use the same upstream as opposed to defining multiple upstreams with identical servers.by Ensiferous - Nginx Mailing List - English
Sounds like it was a browser caching issue. Browsers cache aggressively so always test with curl when you're making changes.by Ensiferous - Nginx Mailing List - English
Hi, You can do this with http://wiki.nginx.org/HttpCoreModule#post_action and http://wiki.nginx.org/HttpCoreModule#.24request_completion Sincerely, Martin Fjordvaldby Ensiferous - Nginx Mailing List - English
having fastcgi_buffers 0 0 and fastcgi_max_temp_file_size 0 should make nginx not buffer. I say in theory because I have no idea whether fastcgi_buffers can actually be set to zero.by Ensiferous - Nginx Mailing List - English
The latest version of upload progress module is 0.8.2 so you should upgrade to that to begin with. If that doesn't solve the problem then I documented my install and progress bar here: http://blog.martinfjordvald.com/2010/08/file-uploading-with-php-and-nginx/ That's almost exactly the code I have in production working just fine, so maybe you can use it as a reference to see if you are missing aby Ensiferous - Nginx Mailing List - English
Your error is not in your Nginx configuration. Are you sure your have configured PHP to listen on port 81, though? This seems like an odd port to start PHP on. Can you paste your php-fpm configuration?by Ensiferous - Nginx Mailing List - English
Hi. There was an API change but I can't remember when it was. Regardless it had only minor effect and pretty much all the modules should work fine regardless. I think what has you confused is how to install 3rd party modules. Nginx only supports compiling in modules statically, which means you have to enable them during compile time. You can't install Nginx and then later add in modules. (withoby Ensiferous - Nginx Mailing List - English
Your should not be using error pages for creating clean URLs, they are for errors, nothing else. See this feature for making clean URLs: http://wiki.nginx.org/NginxHttpCoreModule#try_filesby Ensiferous - Nginx Mailing List - English
It is not meant as a complete configuration. The examples are to highlight specific cases where issues might occur and how to better handle such cases. I agree that it could be worded better but no one should ever use an example from the pitfalls page as their full configuration.by Ensiferous - Nginx Mailing List - English
Hi, The rewrite you use contains /mybb/ but the URI does not. Rewrites work on the URI and not the file path, so unless the information provided is not accurate this is probably why your rewrite does not match.by Ensiferous - Nginx Mailing List - English
Thank you, will update the wiki to match.by Ensiferous - Nginx Mailing List - English
Hi A couple of us in the IRC channel are keeping the wiki updated and we've come across some inconsistent behaviour with server_name. The wiki currently states here: http://wiki.nginx.org/NginxHttpCoreModule#server_name that server_name _; is treated specially for requests with no Host header, however, on the latest dev version this is not so. If a request on the IP or on a domain withouby Ensiferous - Nginx Mailing List - English
James Matthews Wrote: ------------------------------------------------------- > I was wondering what the difference was between > alias and root in the server > block on nginx was? There's a subtle difference. # This will result in files being searched for in /foo/bar/bar as the full URI is appended. location /bar { root /foo/bar; } # This will result in files beingby Ensiferous - Nginx Mailing List - English
All I'm reading here is reiterations of the previous discussion and language elites-ism . This is an extremely old issue, the opinion last time was that this is not something that should be fixed in Nginx. Nginx is a reverse proxy and there may be very valid cases where allowing such URIs make sense. The *real* solution is to fix the php pathinfo setting, it's archaic and shouldn't be used uby Ensiferous - Nginx Mailing List - English