[solved] Auto Index not working

[sophrosyne]

Hi,

lsws 4.1.10
CentOS release 6.2 (Final)

I am getting an error when 'Options +Indexes' is enabled in a directory's .htaccess file. Litespeed is returning a 'Content-Type: handler/x-httpd-php', which triggers the browser to try and download the file.

How can we get litespeed to create the auto index page properly?

Thank you,

[sophrosyne]

Any update/advice?

[webizen]

is this native lsws vhost or apache vhost?

you can try followings and see if your issue goes away.
1. force reinstall 4.1.10
or
2. upgrade to 4.1.11

[sophrosyne]

Originally Posted by webizen

is this native lsws vhost or apache vhost?

you can try followings and see if your issue goes away.
1. force reinstall 4.1.10
or
2. upgrade to 4.1.11

We're using apache vhost. Auto Index is set to "Yes" in litespeed config. Unfortunately force reinstall didn't work, and I don't see a 4.1.11 available. (we're running enterprise)

[sophrosyne]

Any update on this?

[webizen]

You can manually download 4.1.11 package from http://www.litespeedtech.com/litespe...downloads.html since auto-update has not enabled for 4.1.11. run upgrade by unpack the package and run ./install.sh from there (choose 'U' option for upgrade when prompted).

BTW, does the setup work for Apache? We could not replicate the issue in our lab. Hence the question.

[aheadley]

I'm a co-worker of sophrosyne. The 4.1.11 update did not fix the issue, though now instead of the incorrect content type we just get a 404 from litespeed. Here is a (anonymized) snippet of the logs from 4.1.11 with the 404:
http://pastebin.com/2N7CxdAK
The request was for http://example.com/docs/ which points at /home/username/example.com/html/docs/ . There is a .htaccess file in that directory containing (only) "Options +Indexes". It also seems to make no difference if we have the Auto-Index setting set to "Yes" or "Not Set".

[webizen]

Looks like .htaccess is not honored in apache. It would not be honored in lsws either.

2012-03-05 11:16:46.362 [DEBUG] [/etc/httpd/conf.d/vhost_example.com.conf:52] processing direcitve: AllowOverride None.

Change it to something like

AllowOverride All

[aheadley]

Sorry for the confusion, the 404 error was caused by a change the client made to their htaccess file (and the AllowOverride None line). I setup a small test case so that doesn't happen again and it looks like the "Content-type: handler/x-httpd-php" issue is still occuring in 4.1.11 . Here is another snippet of the log from a response with the wrong content-type header:
http://pastebin.com/kH171g3T

And the curl request that generated it:
http://pastebin.com/cMXLvujy

[webizen]

following response header for php is not right.

Content-Type: handler/x-httpd-php

put something like the following in .htaccess to override it.

AddType application/x-httpd-php .php