Serveur web
Get flash to fully experience Pearltrees
Si vous êtes l’heureux possesseur d’un site hébergé sur un serveur dédié , la popularité est une bonne chose mais peut vite s’accompagner d’autres inconvénients comme la saturation des ressources de votre serveur . La solution la plus simple est souvent de passer à une offre supérieure (et donc plus chère), mais cela peut être sans fin ou presque, et les migrations ne sont pas forcément une partie de plaisir. Modifier l’architecture est parfois une meilleure solution et permet de mieux profiter de son hébergement actuel sans trop d’efforts et sans surcoût. Si vous travaillez bien, vous pourrez en plus anticiper le passage à une architecture à plusieurs serveurs.
Nging pour optimiser son serveur web
Installing PHP 5.3, Nginx And PHP-fpm On Ubuntu/Debian | HowtoFo
Follow me on Twitter Since Apache is most of the time a memory hungy process, people started to look for different ways to host their website. Apache is clearly not the only webserver available. A few good examples are lighttpd and nginx. In this tutorial I will show you how to install it on your Ubuntu server.
Gestion erreurs PHP avec Nginx et PHP-FPM | WIIP
Nginx et son compère PHP-FPM forment une superbe alternative au couple Apache + mod_php. Robuste, rapide, simple à configurer. Il n'y a qu'une chose qui m'embêtait jusqu'ici : quand PHP rencontre une erreur fatale (erreur de syntaxe dans un script par exemple), on a droit à une magnifique page blanche avec un code 200. Pas l'idéal pour déboguer et pas trop sympa pour l'utilisateur qui doit se demander ce qui se passe. Et puis j'ai fait ce que j'aurais du faire depuis longtemps : lire la documentation associée à PHP-FPM (RTFM). Ce dernier fournit une directive de configuration nommée fastcgi.error_header à placer dans php.ini qui permet de définir un en-tête qui sera envoyé en cas d'erreur :Lighttpd server - fly light
Security, speed, compliance, and flexibility -- all of these describe lighttpd ( pron. lighty ) which is rapidly redefining efficiency of a webserver; as it is designed and optimized for high performance environments. With a small memory footprint compared to other web-servers, effective management of the cpu-load, and advanced feature set (FastCGI, SCGI, Auth, Output-Compression, URL-Rewriting and many more) lighttpd is the perfect solution for every server that is suffering load problems. And best of all it's Open Source licensed under the revised BSD license . Web 2.0
Apache HTTP Server
The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 2.4.2 of the Apache HTTP Server ("Apache"). This version of Apache is our 2nd GA release of the new generation 2.4.x branch of Apache HTTPD and represents fifteen years of innovation by the project, and is recommended over all previous releases. This version of Apache is principally a security and bug fix release. This version of httpd is a major release of the 2.4 stable branch, and represents the best available version of Apache HTTP Server. New features include Loadable MPMs, major improvements to OSCP support, mod_lua, Dynamic Reverse Proxy configuration, Improved Authentication/Authorization, FastCGI Proxy, New Expression Parser, and a Small Object Caching API.
Dotdeb - depot serveur LAMP pour Debian
The PHP development team is proud to announce the immediate release of PHP 5.4.0 . This release is a major improvement in the 5.x series, which includes a large number of new features and bug fixes. Some of the key new features include: traits , a shortened array syntax , a built-in webserver for testing purposes and more. PHP 5.4.0 significantly improves performance, memory footprint and fixes over 100 bugs. For users upgrading from PHP 5.3 there is a migration guide available here, detailing the changes between those releases and PHP 5.4.0 .Cherokee supports the most widespread Web technologies: FastCGI, SCGI, PHP, uWSGI, SSI, CGI, LDAP, TLS/SSL, HTTP proxying, Video streaming, Content caching, Traffic Shaping, etc. Download Cherokee 1.2.101 Read the Documentation
Cherokee Web Server
www or not www, that is the question...
Javascript servers
HTTP/1.1: Status Code Definitions
Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message.