Use the Apache Proxy directive improved safety LAMP

Listing 4. facade Apache instance of Apache configuration # StuffeveryApacheconfigurationneedsLockFile/var/lock/apache/accept.www-data.lockPidFile/var/run/apache.www-data.pidServerNamenecessaryevil.facade.serverDocumentRoot "/home/www-data" # EssentialmodulesLoadModuleproxy_module/usr/lib/modules/apache2/usr/lib/mod_proxy.soLoadModuleproxy_http_module/apache2/modules/mod_proxy_http.so # WhichusertorunthisApacheconfigurationasUserwww-dataGroupwww-data # Thesemustbesetelsethehostisn'tpassedcorrectlyUseCanonicalNameO ProxyViaOnProxyRequestsO # Thismustalsobeset, thoughit'sonlyanoptioninApac2ProxyPreserveHostOn # TheIP/portcombinationtolistenonListen9.20.1.1: 80 # Usingname-basedvirtualhostingallowsyoutohostmultiplesitesperIP/portcomboNameVirtualHost9.20.1.1: 80 # Configurationtoforwardrequestsforstartup.tld ServerNamewww.startup.tldServerAliasstartup.tldProxyPass/http://127.0.0.2:10000/proxypassreverse/http://127.0.0.2:10000/proxypassreverse/http://www.startup.tld:10000/proxypassreverse/http://startup.tld:10000/#configurationtoforwardrequestsforreckless.tld ServerNamewww.reckless.tldServerAliasreckless.tldProxyPass/http://127.0.0.2:10001/proxypassreverse/http://127.0.0.2:10001/proxypassreverse/http://www.reckless.tld:10001/proxypassreverse/http://reckless.tld:10001/is important to note here the ProxyPreserveHost directive.

This instruction is provided by Apache2, it resolves to the correct HTTP header to the back-end server. Therefore, we strongly recommend that you use an instance as a facade Server Apache2. Run the sample configuration root user should run each configuration. Apache will be specified in the configuration file, and use it for all the processes associated with the host. 5. start the sample server/usr/sbin/apache-f/etc/apache/startup.tld.con/usr/sbin/apache-f/etc/apache/nimrod.tld.con/usr/sbin/apache2-f/etc/apache2/facade.tld.conmod_proxy method restrictions it is important to note that the method described in this article shall not apply to require SSL connections. This is because the SSL protocol does not allow the domain Web hosting. Because of this limitation, any SSL host must be implemented in an appropriate manner, so that each SSL domain using its own IP/port combination. This limit on all Apache configuration are present, use the solution of the Apache is no exception. Still in their owner's user ID to run SSL domain. Closing remarks in this article, using Apache's mod_proxy module builds an environment, in this context has a facade server forwards the request to the two back-end server. You can on a range of back-end server in the same way. This approach enables system administrators to reduce potential security risks, while maintaining PHP and other tools provide flexibility. Reference suEXECsupport: from Apache direct access to documents, learning in the users develop and run private CGI or SSI program how to reduce security risks. MetuxMPMWiki: Learn about this module and to ApacheWeb Server MultiPlatformModule (MPM) and subsequent versions PerchildMPM. IntroductiontoLAMPtechnology (JonoBacon, developerWorks, May 2005): this tutorial describes Linux-Apache-MySQL-PHP (LAMP) Web development framework that helps you solve common business problems. DeveloperWorksWeb development div.: read developerWorks on LAMP and other Web development technologies. Linux zone: check here for developerWorks reference to learn about the latest Linux technologies. Technologybookstore: Browse on these topics and other technical topics of the book. DeveloperWorks technical events and webcasts: pay attention to these activities, as to speed up the progress of learning and to improve the difficult software project development, quality and results. About the author NickMaynard in 2003 graduated from the Science, Technology ImperialCollege and Medicine professional, subsequently joined IBMUKLtd., the following have been IBMHursley ScenarioAnalysisLab work. His expertise is Linux, Web services, and business integration technologies. You can contact with Nick & nbspnick.maynard@uk.ibm.com.