Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:apache:cpanel [2014/04/22 15:26]
Kevin Fwu
+++ litespeed_wiki:apache:cpanel [2015/07/20 18:37]
Michael Alegre removed
@@ Line 7: / Line 7: @@
 This wiki will address some commonly used features for your LiteSpeed Web Server/WHM installation. The installation process is covered in our [[litespeed_wiki:cpanel:auto-installer|auto-installer wiki]].
-**Note:** For free support for issues using LSWS with cPanel/WHM (i.e. problems that you have verified do not occur when you switch back to Apache), please use the [[http://www.litespeedtech.com/support/forum/|LiteSpeed forum]]. cPanel support will not handle LiteSpeed Web Server issues.
+**Note:** For free support of LSWS please use the [[http://www.litespeedtech.com/support/forum/|LiteSpeed forum]]. If you have an issue with cPanel (even while using LSWS) please contact cPanel support. They are fully trained to handle LiteSpeed Web Server.
@@ Line 33: / Line 33: @@
 ===== Run Apache behind LSWS for missing features =====
-There are some rarely used Apache features which are not supported by LSWS, like "Server Side Include", full "mod_perl" functionalities, mod_svn, etc., don't worry, LSWS can forward requests to Apache running behind LSWS. For example, to forward request of SSI page with suffix "shtml" to Apache, do the following:
+There are some rarely used Apache features which are not supported by LSWS, like full "mod_perl" functionalities, mod_svn, etc., don't worry, LSWS can forward requests to Apache running behind LSWS. For example, to forward request of svn pages to Apache, do the following:
   - Listening port of apache should be changed to 79 for HTTP and 442 for HTTP.
   - "Apache Port Offset" configuration in LSWS should be changed to "1", so LSWS will use port 80 and 443.
-  - Set "Apache Handled Content" configuration to ".shtml", this will off load all request to *.shtml to backend Apache, if you want to have apache handle request with certain URL prefix, for example, a svn repository under URI "/svn/", then you can set "Apache Handled Content" to ".shtml, /svn/" to let Apache handle both *.shtml and /svn/*
+  - If you want to have apache handle request with certain URL prefix, for example, a svn repository under URI "/svn/", Set "Apache Handled Content" configuration to "/svn/", this will off load all request to /svn/* to backend Apache.
 :!: Make sure "Port" directive has been changed to the port being used.
-Restart Apache and LSWS, SSI pages should be served by backend Apache now.
+Restart Apache and LSWS, svn pages should be served by backend Apache now.
 ===== FrontPage Extension =====
-To make FrontPage Extension work properly with LSWS, you need to the ownership and permission of //public_html/_vti_pvt/service.pwd// for each account. //service.pwd// was owned by $user:$user with permission of 0600, you need to change it to $user:nobody with permission of 0640.
+To make FrontPage Extension work properly with LSWS, you need to change the ownership and permission of //public_html/_vti_pvt/service.pwd// for each account. //service.pwd// was owned by $user:$user with permission of 0600, you need to change it to $user:nobody with permission of 0640.
 To fix the permission, administrator must execute two shell commands only once, if those changes are overwritten later by cPanel updates, you need to execute it again. (those are contributed by one of our users)