My site is generally doing exactly what I want. Periodically I'll see some errors in the log. I'm trying to determine if these indicate problems in my config, or potential attacks, or simply a broken client. The last few lines in my log: 2016/10/05 14:38:37 17912#0: *17824 invalid url, client: 195.154.181.113, server: amfes.com, request: "HEAD /robots.txt HTTP/1.0" 2016/10/05 19:4by HeavyThumper - Nginx Mailing List - English
I thought I had done both...not seeing any difference in behaviour. --- Daniel On 2015-08-26 14:08, Maxim Dounin wrote: > Hello! > > On Wed, Aug 26, 2015 at 12:33:48PM -0700, dmiller@amfes.com wrote: > >> I have several virtual servers operating with php-fpm perfectly fine. >> Buffering/caching with Wordpress is great. But now... >> >> I'm trying to implemby HeavyThumper - Nginx Mailing List - English
I have several virtual servers operating with php-fpm perfectly fine. Buffering/caching with Wordpress is great. But now... I'm trying to implement a new site that uses php for server-side events to stream live updates to clients. This is, I believe, properly done with an infinite loop in php that will send events as they occur. The problem is the events seem to be getting buffered and doby HeavyThumper - Nginx Mailing List - English
I have a "standard" location block for my php directives... # Pass all .php files onto a php-fpm/php-fcgi server. location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$; include fastcgi_params; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_pass php; } But...I want to set a php_value for aby HeavyThumper - Nginx Mailing List - English
What is the difference between: location /admin { } vs. location ~ /admin(/.*) { } The first seems cleaner, and I assume runs faster - but do they process differently? -- Daniel _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby HeavyThumper - Nginx Mailing List - English