Hello everyone,
Is it just me or new installations of custombuild in suphp mode have the following problems?
1. mod_rewrite directives are plain ignored (that in spite of the same directives working fine in Custom HTTPD Configurations, that is, when they are located within vhost definition).
2. htscanner simply DOESN'T WORK.
During testing suphp builds we have encountered one nasty problem: .htaccess files cannot be used with suphp.
This obviously prevents much of software that needs setting peculiar php_flag* values or uses rewrite engine in .htaccess files from working.
Now, this problem can be worked around by using php extension called "htscanner", http://pecl.php.net/package/htscanner .
However, we have found for reasons have been unable to trace so far, htscanner simply doesn't work in httpd/php compilations as ran by ./build script in custombuild.
We have tried it on several hosts, including combinations such as:
- Apache 2.2 / PHP5 (suphp/fastcgi of course)
- Apache 2.0 / PHP4
It just doesn't work: either it produces 500 error, or it ignores settings if configured according to docs:
da8 (87.204.147.158) /home/da8/domains/da8.promo.pl/public_html % cat .htaccess
# <IfModule mod_suphp.c>
<IfModule mod_php.c>
php_flag allow_url_fopen off
php_flag register_globals on
php_admin_flag safe_mode off
php_admin_flag allow_url_include on
php_flag allow_url_include on
</IfModule>
I found that patch for apache 2.0.59 works fine, i.e. after applying the patch and recompiling apache an error is no longer thrown if <IfModule mod..> directives are not present in .htaccess.
However, the php_flag* vars are still completely ignored as if they weren't there at all. When php is compiled in CLI mode they work of course.
Martynas, I would appreciate if you looked at this issue, because inability to use .htaccess is a show-stopper for us, too much software out there is using .htaccess files by default (joomla installers for instance) for us to be able to say to our customers ".htaccess files just don't work here, sorry".
Is it just me or new installations of custombuild in suphp mode have the following problems?
1. mod_rewrite directives are plain ignored (that in spite of the same directives working fine in Custom HTTPD Configurations, that is, when they are located within vhost definition).
2. htscanner simply DOESN'T WORK.
During testing suphp builds we have encountered one nasty problem: .htaccess files cannot be used with suphp.
This obviously prevents much of software that needs setting peculiar php_flag* values or uses rewrite engine in .htaccess files from working.
Now, this problem can be worked around by using php extension called "htscanner", http://pecl.php.net/package/htscanner .
However, we have found for reasons have been unable to trace so far, htscanner simply doesn't work in httpd/php compilations as ran by ./build script in custombuild.
We have tried it on several hosts, including combinations such as:
- Apache 2.2 / PHP5 (suphp/fastcgi of course)
- Apache 2.0 / PHP4
It just doesn't work: either it produces 500 error, or it ignores settings if configured according to docs:
da8 (87.204.147.158) /home/da8/domains/da8.promo.pl/public_html % cat .htaccess
# <IfModule mod_suphp.c>
<IfModule mod_php.c>
php_flag allow_url_fopen off
php_flag register_globals on
php_admin_flag safe_mode off
php_admin_flag allow_url_include on
php_flag allow_url_include on
</IfModule>
I found that patch for apache 2.0.59 works fine, i.e. after applying the patch and recompiling apache an error is no longer thrown if <IfModule mod..> directives are not present in .htaccess.
However, the php_flag* vars are still completely ignored as if they weren't there at all. When php is compiled in CLI mode they work of course.
Martynas, I would appreciate if you looked at this issue, because inability to use .htaccess is a show-stopper for us, too much software out there is using .htaccess files by default (joomla installers for instance) for us to be able to say to our customers ".htaccess files just don't work here, sorry".