Search results

when did tests in admin console, I also experienced some difficulty to make it working well. although it finally got working, there are some strange behaviors observed. for example, to make the change effective, restarting lsws not enough, must stop and then start lsws. --- but not sure it's...

tested, with only 1 line in .htaccess when access through http://domain.com/p.htm?f=/etc/passwd return as expected. in error.log:

assume the document root is /home/user1/public_html do you have a file /home/user1/public_html/etc/passwd ?

can you give more detail about 700, remote user? for example, a.php's permission is 700 however, only user1 can access and execute a.php, but user2 etc can't.

how do you configure it in httpd.conf? can you paste this part here? it's easier to discuss with an example.

I think you've done it in your first post:

modify .htaccess, without restarting web server

features and difference between standard and enterprise edition: http://www.litespeedtech.com/litespeed-web-server-editions.html another reference: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:all_about_licenses

are you using apache http.conf or litespeed native configuration?

yes, this is the test result.

"forcing a re-install of 4.0.16" -- as the referred thread suggested.

"Site Domain" tip:"If not set, the name of this virtual host will be used" so looks the value can be empty. please try: edit lsws/admin/html/classes/ws/DTblDef.php change line 1888: to see if it finally works.

please refer: http://www.litespeedtech.com/support/forum/showthread.php?t=4221

did tests on our lab. in php suExec mode, lsphp5 run as user's username, if the php script is readable by this user, then it'll be executed. for example, it's owned by root, but readable by other users. so this script can be read by lsphp5 and executed. assume this script is under...

if it's lsws 4.0.6, can you upgrade to latest 4.0.15/16. since there is a security issue on 4.0.14 and below. also considering upgrade php to 5.2.14? see if the issue still there.

so the issue should not exist(or not easy to detect) on litespeed + PHP suExec?since lsphp process is not persistent in this case

Thanks for the update. I'd mark the thread as "resolved"

how about just selecting "Yes"

php suExec enabled?

please be more specific about the issue, so that we can reproduce it at our lab.