I would just like to confirm that Nginx 1.6.0 packages for Centos 6 are compiled with SPDY support.by kustodian - Nginx Mailing List - English
We solved this problem like this: try_files $uri $uri-404; This would first check if the php file exists, and if not it would try to open that same php file but with "-404" appended to it, so the user would still get a 404 status code, but it would also log what file was called. I hope this helps. P.S. Sorry for replying to this topic 2 years later, but this is one of the topicsby kustodian - Nginx Mailing List - English
It would be awesome if the repository would host two versions of the nginx package, one with SPDY for 6.5+ and one without it for older versions. You would need to build two versions, but it would be extremely easy to add this support, you would just need to create symbolic links 6.1, 6.2, 6.3 and 6.4 to point to directory 6 (for the non-SPDY version) on this URL http://nginx.org/packages/centoby kustodian - Nginx Mailing List - English
Hi, Nginx 1.4.0 added support for SPDY to the stable version, so my question is why is SPDY not enabled in the packages from the Nginx official repository? I'm explicitely talking about the Centos packages, I haven't tried others. Regards, Strahinjaby kustodian - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Sun, Oct 28, 2012 at 05:48:30PM -0400, kustodian wrote: > > > Sorry for a late reply and thanks for your help. I did update the > wiki > > documentaion http://wiki.nginx.org/HttpCoreModule#location, I hope > it is ok > > and that location matching will now beby kustodian - Nginx Mailing List - English
Sorry for a late reply and thanks for your help. I did update the wiki documentaion http://wiki.nginx.org/HttpCoreModule#location, I hope it is ok and that location matching will now be clearer to new Nginx users.by kustodian - Nginx Mailing List - English
I would recommend that the documentation for location matching is updated http://wiki.nginx.org/HttpCoreModule#location, explicitaly the example. It should contain a conventional strings besides the root '/' of the site: location = / { # matches the query / only. [ configuration A ] } location / { # matches any query, since all queries begin with /, but regular # expressions anby kustodian - Nginx Mailing List - English
Thanks for the answer. It would be so cool if the options 'log_not_found' had a third option which would be a path to the file where to store these errors.by kustodian - Nginx Mailing List - English
You could also define index inside the server block, outside the location block: server { index index.php; location ... location ... }by kustodian - Nginx Mailing List - English
Well you didn't give us anything to work one. First of does that file exist in the same directoy where test.php is. Can you provide your ngnix.conf, maybe you have some redirects for eather php files, or for css files. Are permissions ok? Maybe Nginx cannot read that file? It could be many things, but you need to give us more information, if you would like to get some help.by kustodian - Nginx Mailing List - English
I have been trying for a whole day to figure out how to redirect 404 errors to a separate log file. I managed to do this in the server directive: error_page 404 = @404; location @404 { error_log /var/log/nginx/404.log; } This does write all 404 errors to 404.log, but the problem is that it also writes these errors in the default error.log, and I don't want that. I want 404 errorby kustodian - Nginx Mailing List - English
Thank you very much for the reply. I was trying everything, I searched everywhere and I couldn't find the solution. Just to note for others, setting "catch_workers_output = yes" doesn't work, you can either patch php with a fix provided in the bug https://bugs.php.net/bug.php?id=61045, or use PHP 5.3.8, which I would recommend since the patch didn't come from the official PHP developeby kustodian - Nginx Mailing List - English
I have recently migrated my Nginx+PHP-FPM server from a Centos 5 to a Centos 6 server and I basically migrated the whole configuration from the old server to the new one with minor changes. I compiled the newest versions of Nginx (1.0.14) and PHP (5.3.10), Centos 5 had 1.0.2 and 5.3.2. The problem is that Nginx doesn't log FastCGI errors in its error.log, it's logging it's own errors without aby kustodian - Nginx Mailing List - English
If you isntalled the service script you could just run "service php-fpm reload".by kustodian - Php-fpm Mailing List - English
Thanks for a fast reply I will try to tweak all those settings. Max number of file descriptors is already very high, so that shouldn't be an issue. fs.file-max = 3240184 I increased other settings as well in sysctl.conf I think the main problem was the listen.backlog = 4096 setting, which wasn't set since I thought that the default setting -1 which means that it reads the system backloby kustodian - How to...
I was looking everywhere, but I could never find a good guide that explains how to configure Nginx with PHP-FPM for a heavy server load, so I hope this is the place where I will find my answer. I have a 24 core server with 32GB RAM with Centos 5.6 which is running Nginx 1.0.2 web server with PHP-FPM (PHP 5.3.5) which is hosting a website that is running some very easy and fast php scripts whichby kustodian - How to...
I have started using Nginx as my main web server just a few months ago, but I'm enjoying it from the first day :)by kustodian - New Member Introductions