auto index problem

[art182]

hello. i've read this post http://www.litespeedtech.com/support...43&postcount=4

~:
mv /usr/local/lsws/share/autoindex /usr/local/php5/
cd /usr/local/lsws/share/
ln -s /usr/local/php5/autoindex autoindex

but still don't work

log:
[config:vhostub.kage.pl] Path of context location contains symbolic link or ownership does not match:/usr/local/lsws/share/autoindex/

where is the problem ?

sorry for english

[mistwang]

You probably has turned on this
http://www.litespeedtech.com/docs/we...heckSymbolLink

try turning it off.

[art182]

Follow Symbolic Link

No
Check Symbolic Link

No

and still

[config:vhost: pub.kage.pl] Path of context location contains symbolic link or ownership does not match:/usr/local/lsws/share/autoindex/

hmm ?
--------
If I change directory of autoindex to default ( /share/autoindex; no symlink )
and disable open_basedir no error in logs but

error 403 :/


edit:
ohh :

[83.220.100.17:15248-1#pub.kage.pl] Scripting is disabled for VHost [pub.kage.pl], context [/_autoindex/], access denied.

php must be on ?

so how can i on autoindex and off php for one vhost ?

[mistwang]

You can try latest 3.3.18 release by change the version number in the download link.

PHP scripting is enabled under that directory while it is disable for the rest of the site.

[art182]

a have this same problem with version 4.0.2

Follow Symbolic Link - No
Auto Index - Yes

and Error 403

[mistwang]

Please try the latest 4.0.3 build by changing the version number in the download link.

[slimak]

The problem still occur for us. We get the "403 Forbidden" error for autoindex at LSWS 4.0.6, 4.0.7 and 4.0.9. The version LSWS 4.0.1 work properly without error.

[mistwang]

Maybe change PHP suEXEC to "User's home directory Only" will fix that.
http://www.litespeedtech.com/docs/we...ral/#phpSuExec

[slimak]

No, in "User's home directory Only" problem still occur.

The Follow Symbolic Link is set to Yes (tried also set to No).
The Check Symbolic Link is set to No.

At the same configuration it was/is working in version 4.0.1 and earlier.