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. Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. 10.1.1 100 Continue The client SHOULD continue with its request. 10.1.2 101 Switching Protocols 10.2 Successful 2xx - Date
Here With Me sur son nouveau serveur ! | Here With Me
Si vous lisez ce message, c’est que vous consultez mon blog depuis le nouveau serveur ! Parlons un peu du nouveau serveur… C’est un dédié OVH dont voici quelques caractéristiques techniques: Intel Core2Duo E6550 64 bits 2 Go DDR2 2x 250 Go SATA2 RAID 0/1 100 Mbps Logiciellement parlant… nous avons fait une configuration exotique: Debian Etch 64 bits MySQL 5 PHP5 via FastCGI Bind 9 Serveur HTTP Nginx Ruby 1.8Mongrel Python 2.4 Postfix Courier (POP, IMAP) Spamassassin Amavis Pure FTPD Voilà pour le gros des logiciels. Ci-dessous les guides utilisés pour arriver à nos fins: Si vous avez des suggestions ou des questions… ;)
Installing PHP 5.3, Nginx And PHP-fpm On Ubuntu/Debian | HowtoFo
Version 1.1 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. Ready? Step 0 - Preliminary Notes In order to complete this tutorial, I assume you have installed a base system of Debian or Ubuntu. Step 1 - Nginx Installing nginx is the first step we have to do. sudo apt-get install nginx The default vhost has to be changed in order to work properly. sudo vim /etc/nginx/sites-available/default A nice starting point for your config is: Ok, we're done here. Step 2 - Installing PHP Many sites rely on PHP for providing them dynamic content, whether this is a wiki, forum software, weblog or something entirely different. If you are running Ubuntu, we first have to resolve two dependencies required for the dotdeb packages. For Debian you won't have to do this! cd /tmp wget
Guide to Webserver SSL Certificates @ Calomel.org - Open Source
Home RSS Search July 15, 2013 Welcome. The purpose of this guide is to clearly explain the reasons you may want to use a Secure Socket Layer (SSL) certificate on your webserver. While researching SSL certificates for use on our site we were constantly bombarded by useless marketing nonsense. Why would one buy a SSL certificate ? The primary reason for using a SSL certificate is to encrypt traffic between your webserver and the client with a "trusted" key verified by an independent third party. If you decide to sign your own ssl certificate and not use an independent Certificate Authority then clients will get an error every time they connect to your site. What you can and can not expect from a https SSL certificate ? A certificate bought from a trusted Certificate Authority simply means a client can verify the certificate's validity through a third party. A SSL certificate simply says that the person or persons who bought the certificate is the same person or persons that own the domain.
Gestion erreurs PHP avec Nginx et PHP-FPM
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). ; Dans php.ini fastcgi.error_header = "HTTP/1.0 550 Script Error" On peut ensuite demander à Nginx d'associer ce code avec une URI : # Dans nginx.conf server { [..] error_page 550 /550.html; [..] } On peut afficher de cette façon une page plus explicative pour l'utilisateur et pour le débogage. Vous pouvez tester le fonctionnement avec le script PHP suivant qui comporte une erreur de syntaxe :
Nginx, serveur WEB - Diablotins.org
Nginx est organisé en modules; chacun apportant une fonctionnalité. Installez le port www/nginx. Le Makefile proposant plusieurs options de construction, nous n'activerons que: HTTP_MODULE "Enable HTTP module" on HTTP_REWRITE_MODULE "Enable http_rewrite module" on HTTP_SSL_MODULE "Enable http_ssl module" on HTTP_STATUS_MODULE "Enable http_stub_status module" on WWW "Enable html sample files" on Le reste étant déasctivé (off). ceci valide les HTTP (essentiels), la réécriture d'URL (ça peut servir), le SSL sur HTTP et les statistiques. Une fois le port installé, vous trouverez les fichiers de configuration dans le catalogue “/usr/local/etc/nginx”. Éditez “/usr/local/etc/nginx/nginx.conf” pour configurer le serveur; le wiki en fourni quelques exemples ainsi qu'une documentation des directives des modules pour, par exemple, le module “HttpCore”. La syntaxe du fichier de configuration n'est pas vraiment documentée (du moins en anglais) et ce qui suit n'est qu'une déduction. Contexte principal #!
Lighttpd server - fly light
Webserver Optimization and Bandwidth Saving Tips @ Calomel.org -
Home RSS Search March 03, 2013 Running a webserver can be a rewarding experience and also a trial in patience. Data Compression Data compression is the process of encoding information using fewer bits (or other information-bearing units) than an un-encoded representation would use through use of specific encoding schemes. Apache and lighttpd both have the mod_compress module. The web server use mod_compress will only compress a page when it is asked for at least once. The draw back of any type of compression is the time it takes for the server to encrypt the data and for the receiving client to de-crypt it. Typical savings on compressed text files range from 60% to 85%, depending on how redundant the code is. Take a look at implementing mod_compress or mod_deflate on your webserver. Expires headers - Caching Caching is the temporary storage of frequently accessed data in higher speed media, like ram or local disk, for more efficient retrieval. The If-Modified-Since request header
Apache HTTP Server
Dotdeb - depot serveur LAMP pour Debian
