PUBLIC MARKS with tags apache & web

Apache has fast become one of the most commonly used web server solutions today. With its use comes the ability to manipulate the behaviour of your site in certain ways (server-side) from a type of file called .htaccess. This easy to read guide covers the various commands, and possibilities of using such a file.

How to Succeed With URLs

The Apache Jakarta Tomcat 5 Servlet/JSP Container Documentation Index

Domain Technologie Control (DTC) is a GPL control panel for hosting. Using a web GUI for admin and accounting all hosting services, DTC can delegate the task of creating subdomains, email, and FTP accounts to users for the domain names they own. DTC manages a MySQL database containing all the hosting information. It has support for many programs (bind 8 and 9 and compatibles, MySQL, Apache 1.3, php4, qmail, postfix 2, courier, dovecot, proftpd, webalizer, mod-log-sql, etc.) through config files and/or MySQL plugins (when the service is non-critical). It can also generate backup scripts, calculation scripts, and config files using a single system UID/GID and monitor all traffic accounting per user and per service. Since version 0.12, DTC is fully skinable and translated into several languages (Chinese, English, Spanish, French, Dutch, German, Italian, Russian, Hungarian, Romanian and Polish).

這個祕密基地必須要有二個檔案： .htaccess 設定檔 .htpasswd 帳號、密碼檔

ModSecurity Console is a network-based console designed to collect logs and alerts from remote ModSecurity sensors in real-time, providing security analysts with the support they need to keep their web systems secure.

Pour diverses raisons (optimisation de site, faciliter la mémorisation des liens, cloaking, etc.), il peut être souhaitable de modifier la forme que prennent les liens d'un site Internet, sans pour autant changer toute la structure des pages physiques. C'est ce que permet la réécriture dynamique de liens, alias URL Rewriting.

Here is a simple cheatsheet for the .htaccess file

A Free, Web-based Feed Aggregator

This tutorial shows how to set up a two-node Apache web server cluster that provides high-availability. In front of the Apache cluster we create a load balancer that splits up incoming requests between the two Apache nodes. Because we do not want the load balancer to become another "Single Point Of Failure", we must provide high-availability for the load balancer, too. Therefore our load balancer will in fact consist out of two load balancer nodes that monitor each other using heartbeat, and if one load balancer fails, the other takes over silently

Tout est dans le titre.