you mean above rewriterules not work for latest lsws 4.2.3, but works for 4.2.2 (or before)?
Yap. That's exactly what I wanted to say, but frankly I cannot predict now
during which LSWS version upgrade this functionality was lost.
On one server running till now with LSWS 4.2 everything is fine.
On 4.2.3 it is not. If it's working on 4.2.1 or 4.2.2 I can't say.
I'd rather not to try any rollbacks without scheduling
maintenace window during the night,
but it may be done if you want me to do that...
pls enable rewrite logging in httpd.conf by adding following in the vhost section
Then do 'grep "REWRITE" /usr/local/apache/logs/error_log' to see if it is the case.
I did what you asked and it showed me nothing realted to that particular rewrite rule.
AFAIR on DirectAdmin based servers LSWS was accepting rewrite rules only in two places:
Nowhere in between.
AFAIS the case is that when user has his own rules in public_html,
any other rewrite rules ( like the one above GEOIP based which we use ) placed in /home/username/.htaccess
doesn't work - although you may still insert for ex. deny/allow rules there and they will be taken into consideration.
Moving users .htaccess file outside public_html ( just for testing ) resolves this issue and this rewrite rule start beeing debuged ( and in fact triggered ) correctly by LSWS.
error log for DA is /var/log/httpd/error_log (was assuming you use cpanel).
just add "RewriteLogLevel 9" to /usr/local/directadmin/data/users/test/httpd.conf (user's vhost httpd.conf) to rewrite debugging.
I did that.
Rewrite debug showed up in /var/log/httpd/domain/domain.com.error.log.
The case is that if there are any rewrite rules placed by the user in
our rules placed in /home/username/.htaccess are not beeing taken into consideration and therefore nod debuged at all.