31–40 of 77 posts
Does anybody know if/when Nginx will support HTTP 1.1? I'd love to be able to use Nginx as the frontend for WebSocket stuff.
What do you mean? HTTP1.1 says nothing about WebSockets, and nginx does support HTTP1.1.
Nginx proxy module only supports http 1.0 basically.
So no proxying to a websocket server yet.
Earlier quoted context omitted.
Congratulations to the team indeed. I'm setting up my next project in this configuration as well and I've found nginx to be a very sweet server. I'll be serving a lot of javascript and css, but using php to handle the utility chores of accessing mysql and couchdb. Even though I'm keeping the apache back-end for this, I confess it's more out of comfort and laziness (and the rush to get it out) than because of some pro…
It really is trivial to set up an fcgi process to run PHP directly from nginx. On the nginx side, something like my config: location ~ \.php { fastcgi_index index.php; include fastcgi_params; fastcgi_pass localhost:55155; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } Then you just need to run php in fcgi daemon mode which is built in, use php-cgi -b localhost:55155 to match that setup... more de…
tl:dr is that the configuration you're suggesting will leave a site open to arbitrary code execution if the site allows for user uploads.
Earlier quoted context omitted.
Great to see a project that is constantly being worked on! Averaged more than 2 releases a month last year with bugfixes and features. An awesome web server.
until very recently, the SVN repo was not made available to the public. AFAIK, there is still no bug tracker. Dont get me wrong, I have several production sites on nginx - but the development methodology makes me very nervous. Cherokee has some of the same objectives as nginx (fast and lightweight) and has a very open development process. Plus, the Cherokee Market is very cool ( http://cherokee-market.com/ ) !
Earlier quoted context omitted.
A socket is probably faster.
Not really the bottleneck if you are running PHP. Linux optimises most of tcp out over the loopback device anyway.
Earlier quoted context omitted.
It really is trivial to set up an fcgi process to run PHP directly from nginx. On the nginx side, something like my config: location ~ \.php { fastcgi_index index.php; include fastcgi_params; fastcgi_pass localhost:55155; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } Then you just need to run php in fcgi daemon mode which is built in, use php-cgi -b localhost:55155 to match that setup... more de…
If you do that, you have to be very careful. I actually did a writeup about this a few days ago that I posted on HN: https://nealpoole.com/blog/2011/04/setting-up-php-fastcgi-an... tl:dr is that the configuration you're suggesting will leave a site open to arbitrary code execution if the site allows for user uploads.
Reaching version 1 is meaningless. Their versioning, like many other projects, is completely botched. "Oh look, we're getting to the high 0.9's, better call the next one 1.0.0!"
Under this scheme, version numbers and the way they change convey meaning about the underlying code and what has been modified from one version to the next.
It's mentioned elsewhere in this thread, but it's not something I knew about beforehand so figured you may also find it helpful.
For me and this big PHP application of ours, switching from just Apache to nginx in front of Apache for PHP execution and serving the rest directly with nginx was the one optimization that brought the best bang for the buck over all the years. Memory usage went down drastically and response times got much better. Additionally, I personally much prefer the syntax of the nginx configuration file (though this really is…
tldr; I hate web server, but I like nginx.
For me and this big PHP application of ours, switching from just Apache to nginx in front of Apache for PHP execution and serving the rest directly with nginx was the one optimization that brought the best bang for the buck over all the years. Memory usage went down drastically and response times got much better. Additionally, I personally much prefer the syntax of the nginx configuration file (though this really is…
Congratulations to the team indeed. I'm setting up my next project in this configuration as well and I've found nginx to be a very sweet server. I'll be serving a lot of javascript and css, but using php to handle the utility chores of accessing mysql and couchdb. Even though I'm keeping the apache back-end for this, I confess it's more out of comfort and laziness (and the rush to get it out) than because of some pro…