Re: Announcing ngx_pagespeed beta 1.5.27.1

2013-04-25 Thread George
Yup http://ngxpagespeed.com/ isn't accessible at all from my end either. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,238650,238656#msg-238656 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Include additional files

2013-04-25 Thread mex
> Ok. So the upstream block has to be in the nginx.conf. I thought I > could > this one export to a separate file, too. yes, you can (include your upstream-config and any other part). you just need to place it into the right context, e.g. inside a http { ... } - block and not inside a server { .

Re: Include additional files

2013-04-25 Thread Jörg Kastning
Ok. So the upstream block has to be in the nginx.conf. I thought I could this one export to a separate file, too. I was wondering why I still got the error message after I deleted the upstream block in nginx.conf and had it only in my included file. So the upstream configuration must be in nginx.c

Re: Announcing ngx_pagespeed beta 1.5.27.1

2013-04-25 Thread Jeff Kaufman
Shoot. Fixed. On Thu, Apr 25, 2013 at 5:43 PM, Constantine A. Murenin wrote: > But the web-site appears to be down; tested from two distinct locations. > > Cns# http_ping -count 4 -interval 1 http://ngxpagespeed.com/; date > http://ngxpagespeed.com/: timed out > http://ngxpagespeed.com/: timed o

Re: Announcing ngx_pagespeed beta 1.5.27.1

2013-04-25 Thread Constantine A. Murenin
But the web-site appears to be down; tested from two distinct locations. Cns# http_ping -count 4 -interval 1 http://ngxpagespeed.com/; date http://ngxpagespeed.com/: timed out http://ngxpagespeed.com/: timed out http://ngxpagespeed.com/: timed out http://ngxpagespeed.com/: timed out --- http://n

Announcing ngx_pagespeed beta 1.5.27.1

2013-04-25 Thread Jeff Kaufman
The Nginx version of PageSpeed is now ready for production use. You can see it in action with examples on our demonstration site: http://ngxpagespeed.com Read more in our official announcement: http://googledevelopers.blogspot.com/2013/04/speed-up-your-sites-with-pagespeed-for.html Ge

Re: upload filename with double quote failure

2013-04-25 Thread Maxim Dounin
Hello! On Thu, Apr 25, 2013 at 03:06:36AM -0400, motto wrote: > Sorry to be annoying, here is part of nginx config: > > # Upload form should be submitted to this location > location /upload_test { > upload_pass @test; > upload_store /usr/local/apps/Opus/temp/upload 1;

Re: Include additional files

2013-04-25 Thread motto
upstream name should be unique per entire config, you could name it in nginx.conf and than reference to its name from different your includes. like: upstream loadbalancer { server 192.168.0.1:8080; server 192.168.0.2:8080; server 192.168.0

Include additional files

2013-04-25 Thread Jörg Kastning
Hi. I have some trouble cleaning up my /etc/nginx/nginx.conf. I have several upstream and server blocks in this file and it becomes a mess. So I tried to write each configuration in a seperate file saved in /etc/nginx/conf.d/loki.conf for example and include them in nginx.conf. I include the file

Re: upload filename with double quote failure

2013-04-25 Thread motto
Sorry to be annoying, here is part of nginx config: # Upload form should be submitted to this location location /upload_test { upload_pass @test; upload_store /usr/local/apps/Opus/temp/upload 1; upload_store_access user:r; upload_set_form_field $upload_f