Migrating a site from IIS6 to IIS 8.5

Helicon Ape provides support for Apache .htacces and .htpasswd configuration files for Microsoft IIS.
User avatar
Posts: 2
Joined: 10 Dec 2014, 18:01

Migrating a site from IIS6 to IIS 8.5

10 Dec 2014, 18:13

Good afternoon,

I have a reather larger client site (220k files, 21go) that need to be migrated from IIS6 to IIS8.5. The current site was already using Helicon Mod_rewrite and was working like a charm in IIS6. When I've first move the site to the new server with IIS 8.5 (Application Pool setting : .net 2.0, 32bit, Integrated) The site was working well, but was taking about 80% of the machine resource everytime a page reload was done.

I've been told that the site absolutly need to function in classic mode to conserver CPU power. So this is what I've tried :

- I first tried to disabled the site in APE, with not success. (Looks like a problem when the site is .net2.0 instead of 4.0?)
- I've removed the files from the hosting plan... Disabled the site in APE... switch the application pool in classic mode... Re enabled APE, and copied the file back in the hosting plan.

After the second step, the mod rewrite was no longuer working, but this site was loading lightning fast....

My problem now is how to enabled mod_rewrite in classic mode..

Thank you for any input your may have!

Sincerely,

Me!

User avatar
Posts: 402
Joined: 06 Mar 2012, 11:59

Re: Migrating a site from IIS6 to IIS 8.5

11 Dec 2014, 09:13

This is not clear to me how Ape was working on Windows 2003 if your site requires classic mode? Helicon Ape is a .NET module and requires integrated mode to run, because in classic IIS mode .NET is not present. Ape can work in both .NET 2.0 and 4.0 pools. You may try to configure Ape manually, same way as you where configuring it on Win 2003 and map ASP.NET engine to "*" as mentioned in installation chapter: http://www.helicontech.com/ape/doc/installation.htm

Another solution for you would be use ISAPI_Rewrite 3 instead of Ape. ISAPI_Rewrite implements only a portion of Ape directives, like mod_rewrite-related directives, so if you are using only URL rewriting functions ISAPI_Rewrite would be enough. But unlike Ape, ISAPI_Rewrite is implemented on C++ using old ISAPI interface, which does not require .NET to operate, so you can use it in classic ASP pool mode. If installing ISAPI_Rewrite will solve your problem, I can exchange your Ape license to ISAPI_Rewrite. Please do not install both Ape and ISAPI_Rewrite on same machine as they may conflict.

Return to Helicon Ape

Who is online

Users browsing this forum: No registered users and 28 guests