Can't open javascript folder on web

[Reppie]

I have a website, wich uses a folder 'javascript' with in there some javascripts.
If i browse to my website and try to access those javascript files in there, i always get a 404.

If i rename the folder 'javascript' to 'script' or something else, i CAN access those files... It seems that the folder 'javascript' gets somewhere blocked, tho i cant find anything in my htaccess or in the IPSConfig3 settings....

Ofcourse, the solution is easy... i just rename the folder 'javascript'.... tho i'm still curious what causes this problem

[till]

There must be some kind of alias or redirect for "javascript" somewhere in a .htaccess or the apache config files. ISPConfig does not add such a alias, so it must have been added by another component.

You can e.g. try to scan all apache config files with the "grep" command for the word "javascript".

[Reppie]

Thanks for your reply, i'll try to search for a 'javascript' term in the config files. I already checked (and removed) the .htaccess file for this website. Is there another (global) .htaccess file i should check?

[till]

There are no global .htaccess files.

[teves]

This thread is old, but I have this issue also on an up-to-date installation of Debian Squeeze (perfect setup) with ispconfig3.
I tried to install flyspray, which worked without errors. But after installation you cannot log in, because all javascript files are not loaded (from the 'javascript' folder; access denied with a 403 error)

I found out that this happens because of the file /etc/apache2/conf.d/javascript-common.conf
It contains the following code:

Alias /javascript /usr/share/javascript/

<Directory "/usr/share/javascript/">
        Options FollowSymLinks MultiViews
</Directory>

But I did not find a hint about what one might do about it. Why does this file exist, what does it do? Can I remove it or comment it out?

Does anyone know?

Thank you!
Regards, Tom

[till]

Please see here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553173

I would comment out all lines in /etc/apache2/conf.d/javascript-common.conf and then add them inside the vhost definition of the debian default vhost /etc/init.d/sites-available/default as suggested in the thread. This will ensure that debian packages which use the default vhost still work without affecting other websites.