FrontPage Extensions & cPanel
 

Hello,
I have problem with using FrontPage Extensions at cPanel server.
I tried to login at http://account_domain/_vti_bin/_vti_adm/fpadmcgi.exe, but there was an error. In _vti_pvt/service.pwd was at first line "# - FrontPage -". When I deleted that comment (this is first problem), I can now login to http://account_domain/_vti_bin/_vti_adm/. When I go to http://account_domain/_vti_bin/_vti_adm/fpadmcgi.exe, I see 404 error. On Apache&cPanel there is working a FrontPage Extenstions Site. That is the second problem. Could you tell me, how could I enable FrontPage Extensions?

Answer
 

Yesterday I do some tests and there is impossible to setup FrontPage Extenstions, when you import configuration from httpd.conf (e. g. cPanel). I did also steps described at: http://www.litespeedtech.com/library.../#qa_frontpage

There is problem with: "The most important configuration is the Domain Names, it must match the domain name part of the URL that you used to access the web page, and otherwise it will not work". When configuration is imported from httpd.conf, then "Domain Names" aren't set. cPanel keeps FrontPage Extensions cofigurations in /usr/local/frontpage/. May you add ability to work FrontPage Extensions with httpd.conf/cPanel configuration?

What is the apache directive used by cPanel to enable frontpage for a vhost?

"FrontpageEnable"? or something else?

Answer
 

None, there is only a one line in httpd.conf about FrontPage:
AddModule mod_frontpage.c

OK, it is the mod_frontpage coming with Microsoft frontpage package, it is like a global switch which enable frontpage for all vhosts. I will add support for that module.

OK, frontpage should work now with the updated package, please give it a try and let me know. Thanks.

Answer
 

There are still some problems:
1. from error.log:
[NOTICE] [FrontPage] //home/user/public_html/_vti_inf.html is missing!
or
[NOTICE] [FrontPage] ownership of //home/user/public_html/_vti_inf.html does not match ownership of document root!
2. the _vti_pvt/service.pwd file have by default permissions 0600, so LSWS can't access to that file. If there is a necessary, I may try to do some changes in cPanel files, which sets permissions to service.pwd.
3. after upgrade lsws, I had an error 403 for all _vti_*/* files
4. now the FrontPage Extensions doesn't work, but I don't know why
4. what will happen if somebody add FrontPage Extentions for his account in cPanel (cPanel isn't reloading lsws after that)?

1. _vti_inf.html related error messages are because frontpage extension has not been installed for that vhost. LSWS tests existances of a few files under document root to make sure frontpage extension is enabled for that vhost. We can skip that test and enable fp extension for all vhost.
Who own the _vti_inf.html as well as all other _vti_*? it supposed to be owned by the same user that own the document root. Probably not required, we can relax the requirement on this.
2. should not matter, as service.pwd is only used by the extension itself running in setuid mode.
3. That's for security reason, direct access to all _vti_*/* files are denied.
4. probably because problem in #1, extension has not been turned on.
5. That's a good question, it will not be enabled as LSWS only verifies this at startup, maybe should just skip the verification.

1. They are owned by the $user:$user. The document root is owned by $owner:nobody
3. Some or even all should be accessible directly.
4. I will check that.
5. That could be a good idea. It could be verified, when somebody will try to use FrontPage Extensions for his site i.e. it will access the _vti_bin dir.

Please give the to be released RC2 package a try

http://www.litespeedtech.com/package...6-linux.tar.gz

It should work better.