Support

 Hi! We have Akeeba Admin Tools Pro installed on a Windows server. This is why the htaccess maker is not shown in Akeeba Admin Tools, right?

But the server administrator of this server claims their server does know how to handle .htaccess files. Not sure how.

Is there a way to use the .htaccess editor on this server?

Kind regards,
Jip

Hi Nicolas,

The windows server uses Helicon Ape (http://www.helicontech.com/ape/). Never heard of it before. Also am I not sure how much of the .htaccess functionality can be used.

One of the modules it uses is mod_rewrite.
http://www.helicontech.com/ape/doc/mod_rewrite.htm

I guess that's the module that provides most of the security features the .htaccess maker uses.

Maybe I'll give it a try using the direct link you provided. The site is not live yet.

Kind regards,
Jip.

Hi Nicolas,

I created a .htaccess file on the windows server with the direct link to the htaccess maker. I needed to delete these parts to make it work:

##### Redirect index.php to / -- BEGIN
RewriteCond %{THE_REQUEST} !^POST
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /index\.php\ HTTP/
RewriteCond %{SERVER_PORT}>s ^(443>(s)|[0-9]+>s)$
RewriteRule ^index\.php$ http%2://www.tijdelijkehosting.nl/ [R,L]
##### Redirect index.php to / -- END

## Disallow access to rogue PHP files throughout the site, unless they are explicitly allowed
RewriteCond %{REQUEST_FILENAME} (\.php)$
RewriteCond %{REQUEST_FILENAME} !(/index[23]?\.php)$
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule (.*\.php)$ - [F]

So I guess it works partially... It seems that some rewrite rules need to be adjusted to make it work. We will dive into that later.

Is there a way to check if the (other) rules created by the .htaccess maker actually work?

I also need to bulld the template and install extra components for this website, so I'm not sure what I will run in to during the creation of this site.

I am not sure if we are actually are going to use it this way when we go live. We'll see.

Kind regards,
Jip Jonker

Ok, thanks. In this case hosting on a Linux server is not possible because this is a client who delvers services to their own clients on windows machines. Like monitoring, applications etc. The are windows specialists... So they do not want their website hosted on a Linux server (or our Linux Server). I told them I would prefer not to do this on Windows, and also that this would probably mean some more problems and less security. But, it's their choice. As long as I get paid for extra time spend on configuration...

And thanks for the tip on the database prefix / table names.