snacktime wrote: > Well I figured out exactly what causes this after getting someone that had the errors to install the firefox livehttpheaders plugin. It's the cookie size. Cookie too large, nginx returns a 400 and doesn't log it. Unfortunately there isn't much we can do about the cookie size. With the fb connect iframe stuff there are other parties setting cookies on our domain. >by Jim Ohlstein - Nginx Mailing List - English
Have you looked at http://wiki.nginx.org/NginxHttpSecureDownload?by Jim Ohlstein - Migration from Other Servers
It was worth looking at. :) If you include: server { listen 80; server_name webmail.domain1.com ; access_log /var/log/nginx/webmail/access.log; location / { proxy_pass http://mail1; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_redirect false; } } in your dby Jim Ohlstein - How to...
I wonder if the wildcard simply isn't being picked up in the webmail.conf file. Please print the output from # /path/to/nginx -tby Jim Ohlstein - How to...
I haven't tried doing it but yes, it shouldn't be too hard. The solution would depend on what method you are using to serve php. If you are going to use fastcgi, then using php-fpm and having a small, separate pool of worker(s) listening on a different socket for each virtual host should work (some people use 9000+UID of the owner of the virtual host). There is a section in php-fpm.conf for &quby Jim Ohlstein - How to...
The rewrites will have to be done nginx style. They are only slightly different than Apache rewrites. They can be entered in either a "server" or "location" block, and can even be within an "if" statement. If you only have one virtual host on the server then putting all of the configuration in your nginx.conf makes sense. With multiple virtual hosts, an entry likeby Jim Ohlstein - Migration from Other Servers
I'm assuming there might be rewrites or cache settings or something along those lines in that block. Maybe not? I don't know that app well enough to say. Fastcgi vs Apache biggest advantages would be memory consumption and (probably) CPU usage. Ridding your server of Apache will get rid of all those threads/processes that Apache spawns.Each time a process is spawned CPU time is used.Nginx has nby Jim Ohlstein - Migration from Other Servers
Yeah, nginx is pretty smart. You tell it what the document root is, you tell it what requests to pass by proxy to Apache (or to php-cgi if you use fastcgi_pass) - in this case anything ending with ".php" and it will serve the static files. So in your nginx.conf you might have something like this: server { server_name your-mu-server.com www.your-mu-server.com; listenby Jim Ohlstein - Migration from Other Servers
I would think it would be all requests also.There isn't anything specific for GET, HEAD, POST, PUT etc, to my knowledge. It probably wouldn't be terribly hard to implement if you know C (but I can't help you there :p). You can restrict your limit to a "location" block which can be a single script if that helps.by Jim Ohlstein - How to...
Have you tried http://wiki.nginx.org/NginxHttpLimitReqModule?by Jim Ohlstein - How to...
sipiatti Wrote: ------------------------------------------------------- > Thanks I will try. But if a match found there is > no need to continue checking the rules, is it? > Anyway from the logic point of view are my rules > correct? The rewrites appear to be. Try using "last" in the vBSEO rewrites as well.by Jim Ohlstein - Migration from Other Servers
Try using "last" instead of "break" in those rules.by Jim Ohlstein - Migration from Other Servers
The ssl module is not built by default. To find out if it's in your package run # nginx -V If ssl support is present you'll see "--with-http_ssl_module" in the configure arguments.by Jim Ohlstein - Nginx Mailing List - English
I think you are looking for something like: http://blog.kovyrin.net/2006/04/29/monitoring-nginx-with-rrdtool/. The wiki at http://wiki.nginx.org/NginxHttpStubStatusModule has the documentation.by Jim Ohlstein - How to...
Andrea Wrote: ------------------------------------------------------- > I have two new questions... i hope you can still > help me :) > > 1) What is the "use epoll" in the config? I > searched on google, but i couldn't understand very > well... i am on ubuntu and i'm using ruby on > rails, should i leave this on? For a home testing server it doesn't muchby Jim Ohlstein - How to...
Hi Andrea, Your English is far superior to my Italian. :) The nginx workers only need read access to your files so as long as permissions are set as 644 for files and 755 for directories then it will work fine. If your application requires files to be written then you need to either change the owner or the permissions.by Jim Ohlstein - How to...
If you installed a package then that package perhaps created the user "www-data"? From the command line you can run # cat /etc/passwd | grep www-data to confirm there is such a user. If you already did that and I'm insulting your intelligence then I apologize. :) You can also run # ps -elf | grep nginx to see what user owns the nginx worker process(es). In any eby Jim Ohlstein - How to...
No irony at all. If Igor wanted one he would have it. I will create it. I hope it is used more than the other non-English forums have been used.by Jim Ohlstein - Site Suggestions
The plan is to introduce keepalive connections to the backend in the 0.8 branch at some point (in other words HTTP 1.1). Since 0.8.0 was just released yesterday it could be awhile before that happens. Of course once that happens there is still no guarantee that Uber Uploader will function correctly. Some upload progress meters work fine with nginx. It simply depends on how they are written.by Jim Ohlstein - Migration from Other Servers
I believe the *default* location is /usr/local/nginx/html but if you use the option "--prefix=PATH" that will set it to whatever you like. If you like the default layout and only want to change the location of the default server, do that in the root directive in nginx.conf: server { listen 80; server_name myserver.com; location / {by Jim Ohlstein - Other discussion
The 504 issue can perhaps be fixed with increasing php max_execution_time and/or max_input_time. You can also try increasing proxy_read_timeout or fastcgi_read_timeout depending on how you are serving php requests. You can find info on these at http://wiki.nginx.org/NginxHttpProxyModule#proxy_read_timeout and http://wiki.nginx.org/NginxHttpFcgiModule#fastcgi_read_timeout. The upload progress baby Jim Ohlstein - Migration from Other Servers
Cliff Wells wrote: > On Tue, 2009-06-02 at 20:37 +0400, Igor Sysoev wrote: > >> Changes with nginx 0.8.0 02 Jun 2009 >> >> *) Feature: the "keepalive_requests" directive. >> > > Added to wiki. > > >> *) Feature: the "limit_rate_after" directive. >>by Jim Ohlstein - Nginx Mailing List - English
Very exciting! Thank you Igor. ------Original Message------ From: Igor Sysoev Sender: owner-nginx@sysoev.ru To: nginx@sysoev.ru ReplyTo: nginx@sysoev.ru Subject: nginx-0.8.0 Sent: Jun 2, 2009 12:37 PM Changes with nginx 0.8.0 02 Jun 2009 *) Feature: the "keepalive_requests" directive. *) Feature: the "limit_rate_aftby Jim Ohlstein - Nginx Mailing List - English
In accordance with my policy of always running the latest development version of nginx on this server we have moved to 0.8.0 which was released today.by Jim Ohlstein - Announcements
Please post your configuration file(s).by Jim Ohlstein - Nginx Mailing List - English
Are you using a video script like Clip-Share or phpMotion?by Jim Ohlstein - Migration from Other Servers
The only problem with using spawn-fcgi, IIRC, is that it will only create one process (unless that has changed). That's fine for a site that doesn't get many requests. With the script at that site the you can launch multiple instances of fcgiwrap and handle multiple concurrent requests.by Jim Ohlstein - How to...
No, I don't think so.by Jim Ohlstein - How to...
I'm not sure what you're asking. The simplest way to find out if your config file is valid is to run # nginx -tby Jim Ohlstein - How to...
@404 or @fallback simply references a location. You can use @whatever. What "try_files" does is it tells nginx to try to serve the listed files in order (in this case your URI as represented by $uri) and if it doesn't find the requested resource then it goes to the location "@...". In the configuration I posted, @404 location is a proxy_pass directive.by Jim Ohlstein - How to...