Hi all,I have a dedicated server supplied by Fasthosts, that runs Fedora Core 3. Its an odd setup - the server runs Fasthosts’ “Matrix Control Panel”. Apache has a central config file (httpd.conf) and then the sites that are hosted on the server are listed in vhost.conf.
A reverse proxy is a gateway for servers, and enables one web server to provide content from another transparently. As with a standard proxy, a reverse proxy may serve to improve performance of the web by caching; this is a simple way to mirror a website.
The base settings are set in the httpd.conf I guess, and then overidden in vhost.conf, and then overidden some more in.htaccess.I am having problems trying to get any modrewriting to work. As soon as I turn “RewriteEngine On”, I get a 500 internal server error.
I look in the error log, and see “.htaccess: RewriteEngine not allowed here”. Apache manual to the rescue!RewriteLog DirectiveDescription:Sets the name of the file used for logging rewrite engine processingSyntax:RewriteLog file-pathbContext:server config, virtual host/bStatus:ExtensionModule:modrewriteRewriteLogLevel DirectiveDescription:Sets the verbosity of the log file used by the rewrite engineSyntax:RewriteLogLevel LevelDefault:RewriteLogLevel 0bContext:server config, virtual host/bStatus:ExtensionModule:modrewriteWhy would you want to use.htaccess anyway? It’s slow and should only be used if you have no access to virtual host and server config. Feenster:Hi,Thanks for the reply - i have put the RewriteLog directives in my.htaccess, as shown in my first post. However, it is when the RewriteEngine is turned on that I get the errors - thus, no log is ever created/updated.Maybe you misunderstood.
RewriteLog cannot be used in.htaccess. It can only go in server config or virtual host. Of course it is only activated when you turn RewriteEngine On.I have multiple sites running on the same server, and want to be as flexible as possible with how I configure them.So does everyone, but the directives should go straight into virtual host config instead.htaccess is read from disk everytime someone loads a page and makes it much slower. It is only made for people who are on shared hosting and have no access to higher level.
If you have root access, avoid using it. Virtual host and server config are read into memory as apache starts up, so they are much faster options.
Hi.D:/wamp/wwwprobably defined above your VirtualHost section as default DocumentRoot and is accessed if no VirtualHost section found or NameVirtualHost is disabled.1) Check that in httpd.conf you have:NameVirtualHost x.x.x.xwhere x.x.x.x is your server IP address2) Change VirtualHost section, so it would look like:ServerName www.mysite.comDocumentRoot d:/wamp/www/mysite3) Check that you access your website by name www.mysite.com, not by IP (that should direct you to default directory server DocumentRoot).Regards,Arty.