View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0009937||phpList 3 application||Configuration||public||08-05-07 10:37||21-06-18 13:00|
|Target Version||Fixed in Version|
|Summary||0009937: Internal Server Error (.htaccess file problems with Apache configurations)|
|Description||This issue will give you an "Internal Server Error" page.|
There are troubles with .htaccess files in phplist and Apache configurations if your Apache is not configured with "AllowOverride All" in httpd.conf file.
Another configuration I found working is "AllowOverride Options AuthConfig Indexes Limit" but this is only possible if you have access to the Apache server config file and this is probably not possible.
A quick FIX is to TAKE AWAY the .htaccess files in dirs "/lists" and "/admin" (and probably in any other dir where .htaccess may reside), but it will open some security related issues. If this is the case, try to use the .htaccess files to authenticate the users that may have access to files and not to deny the files.
bit of a catch 22.
I'd rather not remove the .htaccess files, and open up the system, but yes, it's awkward that it causes the 500 errors. I guess this should be clearly documented with options what to do about it, and what impact that has.
Solution is given in forum and is very simple and clear.
1°) Last line of the htaccess must be commented and becomes :
#php_flag magic_quotes_gpc on
2°) You must create or do a php.ini with these two lines at the root (same place than the htaccess :
it works perfectly and the security is still on.
||well, that may work in some cases, but it's possible the other directives in the file cause a 500 as well.|
This fits for Apache GCI which from what I have read are more protected.
Most servers are set on that way now on the Continent and all big hosting-compagnies are using Apache CGI because it is more protected.
So there is not to delete or change any htacess in other parts of the program.
You wrote :
"well, that may work in some cases, but it's possible the other directives in the file cause a 500 as well. "
I can say, I use the system that I have described and I never get an other 500 error when using the soft.
Moreover the question is from 2007 and it has been resolved with either yourself or people in the forum.
If that system was not running correctly, there should have been people telling it in the forum. The only problem they meet is when they do not respect the architecture /lists and /lists/admin.