Helicon Ape and Classic ASP mode
5 posts
• Page 1 of 1
Helicon Ape and Classic ASP mode
Hello,
Just trialling Ape on IIS8.5 with classic asp websites running application pools in Classic ASP managed pipeline mode and .NET CLR version "No Managed Code".
I've seen a few posts about limitations of Helicon Ape with web servers running in Classic ASP mode. Could you clarify what these are?
After downloading we did a simple trial of using the mod_hotlink feature. We added this code to the top of our .htaccess but other websites are still able to hotlink any image in our /images directory so it does not seem to be working.
SetEnv mod_hotlink
HotlinkProtect /images
Instead we have previously been using this in ISAPI Rewrite 3 to block hotlinkers:
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?mysite.com [NC]
RewriteRule \.(jpg|jpeg|png|gif|css|asp|htm|html)$ - [NC,F,L]
Would like to use Helicon Ape instead of Rewrite as Ape has a lot more features, but need to know if it's going to work with Classic ASP.
Thanks
Just trialling Ape on IIS8.5 with classic asp websites running application pools in Classic ASP managed pipeline mode and .NET CLR version "No Managed Code".
I've seen a few posts about limitations of Helicon Ape with web servers running in Classic ASP mode. Could you clarify what these are?
After downloading we did a simple trial of using the mod_hotlink feature. We added this code to the top of our .htaccess but other websites are still able to hotlink any image in our /images directory so it does not seem to be working.
SetEnv mod_hotlink
HotlinkProtect /images
Instead we have previously been using this in ISAPI Rewrite 3 to block hotlinkers:
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?mysite.com [NC]
RewriteRule \.(jpg|jpeg|png|gif|css|asp|htm|html)$ - [NC,F,L]
Would like to use Helicon Ape instead of Rewrite as Ape has a lot more features, but need to know if it's going to work with Classic ASP.
Thanks
Re: Helicon Ape and Classic ASP mode
We're also seeing this message at the top of the screen in Helicon Ape Manager:
"This application works in the Application Pool running not in Integrated mode. Wildcard mapping to ASP.NET is not configured for this application"
Could you explain what this means so I can review whether it affects us. The websites seem to be running fine with the old .htaccess code from ISAPI Rewrite, so i'm not seeing any functionality not working in Ape that worked in ISAPI Rewrite
"This application works in the Application Pool running not in Integrated mode. Wildcard mapping to ASP.NET is not configured for this application"
Could you explain what this means so I can review whether it affects us. The websites seem to be running fine with the old .htaccess code from ISAPI Rewrite, so i'm not seeing any functionality not working in Ape that worked in ISAPI Rewrite
Re: Helicon Ape and Classic ASP mode
Hello Admins, can I get a reply on this? I am just trialing Ape at the moment and will have to remove it if I can't determine if it's suitable. Just wanted to clarify before the trial runs out. Thanks.
Re: Helicon Ape and Classic ASP mode
Uninstalling the trial guys. Unfortunate I couldn't work out whether it will work for us, as no response here.
Re: Helicon Ape and Classic ASP mode
Hello.
I am really sorry for the delay.
Unfortunately, because Helicon Ape is a .NET module it cannot run in classic ASP mode of IIS as no .NET code can be loaded into the IIS worker in this mode. If you really need to keep your site in Classic ASP mode Ape cannot be used on that site.
I am really sorry for the delay.
Unfortunately, because Helicon Ape is a .NET module it cannot run in classic ASP mode of IIS as no .NET code can be loaded into the IIS worker in this mode. If you really need to keep your site in Classic ASP mode Ape cannot be used on that site.
5 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 8 guests