.htaccess gives internal 500 error
Twan
Joined: 2003-11-27
Posts: 3 |
Posted: Thu, 2003-11-27 18:14 |
High, Each time I put an empty .htaccess file with perm. 777 in the gallery directory, I get a internal 500 error. Removing the file gives access to the setup of Gallery but it requires this .htaccess file... This means I'm not able to finish the installation. Gallery is running at xxlwebhosting (www.xxlwebhosting.nl) in the Netherlands. For more info: http://www.delfshaven.org/gallery/setup/phpinfo.php Can anyone get me out of this loop? Thankx in advance, Twan P.s. I didn't find a forum answer with this exact problem... |
|
Posts: 13451
Twan, so, the reason for putting it back (since it crashes your site) is?
Posts: 3
The reason I put it back is because the setup script requires an empty .htaccess file with 777 rights to finish the setup...
I also checked the error log of the webserver:
[Thu Nov 27 18:26:37 2003] [alert] [client 80.126.0.204] /home/delfshav/public_html/gallery/.htaccess: Invalid command '{\rtf1\mac\ansicpg10000\cocoartf102', perhaps mis-spelled or defined by a module not included in the server configuration
Beats me...
Thankx for the fast response!
Greetz,
Twan
Posts: 3473
empty .htaccess in the gallery directory, not the setup directory.
Posts: 3
I did put it in the gallery dir instead of the setup dir...
In some way apache refuses any connection as soon as there is a .htaccess file...
And I don't have shell access, don't have permission to change httpd.conf etc. (snif)
Greetz,
Twan
Posts: 6
I have the exact same problem running on RedHat 8.0. Did you every get this resolved?
Posts: 8194
Have you deleted the .htaccess file in the setup/ directory?
Posts: 6
No, I hadn't deleted the file, but I seem to have a solution. I edited the .htaccess file and commented out the line:
php_flag session.bug_compat_warn off
The Apache log indicated that the 'php_flag' was an unknown command, so I just tried removing it and it worked.
However, I am unclear if this will come back and bite me in the future. Do I really need this line in the .htaccess file? If so, what should the proper work around be?
Thanks,
Steve