fancyindexing works but not with the domaine name :-(

[nickwe]

Here I can get the directory listing:
http://82.192.74.140/~nickweuser/ephec/
but not here
http://www.nickwe.com/ephec/
where I get my custum "Forbidden page" for an error 403

Those two pages point to exactely the same directory. I've tried a lot of things before coming here. First I chmod the directory 777, so it should be ok to be access and listed. Since I own the server, I can change configuration files of apache. So I enabled fancyindexing for my virtual server domain (nickwe.com) and I also create an .htaccess file that I put in the directory I want the listing. Both method result with the forbidden page :-( It was working before when I didn't use directadmin on an other server and with the same domain name, so I guess it might be a directadmin feature that we should be able to disabled, no?

Well, if you have any idea, don't hesitate.

Thanks o lot,

Nickwe

 

[nickwe]

OK I've succeed All I had to do is replacing manually the line
Options +Includes -Indexes
by
Options +Includes
in the file
/usr/local/directadmin/data/users/nickweuser/httpd.conf
and if you want the change to apply to all your client, just make the same change in
/usr/local/directadmin/data/template/virtual_host*.conf
and dont forget to restart apache in both case

That's it

Nickwe

PS: If someone knows how to do this by directadmin, that would be cool. I can get to the configuration file by: Admin Panel -> Admin Settings -> Customize httpd.conf -> nickwe.com but then I don't know what to do :-(

 

[DirectAdmin Support]

Hello,

In the custom httpd.conf, you'd just add

        <Directory |DOCROOT|>
                Options +Includes +Indexes
        </Directory>

But you'd need to *remove* those Options from the template because the |CUSTOM| token is placed above the Directory setting in the template. That would mean that Indexes would be turned on, then as apache parsed more, the default would be found and it would then be turned off. You could always move the location of the |CUSTOM| token to *after* the <Directory> stuff in the template, then it wouldn't matter.

John

 

[nickwe]

OK thanks a lot, I moved down the |CUSTOM| token, so if a client want me to change the directory listing option, I just change his custom httpd.conf by directadmin.

Nickwe

 

[netswitch]

seems that after this, https isn't working fine anymore.

it shows the "hey it worked" page from the standart apache install instead of the pages users put in private_html.

any idea where it could come from ?