Conversion from Linkfreeze on Windows 2008 Server 64 Bit

[smilie Profile]

Hello,

I am moving my post from the previous topic,
http://www.helicontech.com/community/Linkfreeze_on_Windows_2008_Server_64_Bit-11-3742.html

It's been 2 months and I am still unable to get mod_linkfreeze to properly work on IIS 7 , Windows 2008 64bit. I just purchased a version Helicon Ape to see if I can try maybe and get better response.

I've discussed this via numerous emails with tech support.

My mod_linkfreeze looks like this:

# Migrate from old Linkfreeze to new rules, overwrite ? & = parameters with dashes, "-"
# This will create URLs like /news/news.asp-newsid-12345
SetEnv mod_linkfreeze
LinkFreezeRule --- "*" [ AbsLinks, Redirect, NoSort ]

This works as far as redirecting urls from dynamic to static , majority of the times, and how we want it. for instance,
/news/news.asp?newsid=12345 will be redirected to
/news/news.asp-newsid-12345
(this is how we had Linkfreeze work more than 10 years ago, can't modify it now on a site with 250,000+ pages and hundreds of thousands of links pointing to).

However, when pages load, the links that are already on the page don't get converted to static. They still show dynamic format.

I also have debug turned on, see no errors. Site is running under Integrated Application Pool.

I've been told it is IIS caching and "to turn it off". Unfortunately with 40 different websites running on the server turning it off won't be such a good idea. I tried disabling it just on the website, but I don't think it works (or maybe I missed something). So I am now paying for two servers instead of one for 3 months and trying to figure out my next move.

Looking forward for you suggestions, please.

Thank you for your help!

[Yaroslav]

Hello.

Can you please help me to remember - are your sites run on ColdFusion?

[smilie Profile]

Hi, thanks for replying.

No, it classic asp.
See extension above , .asp

I found other interesting Ape bugs while testing on a new box. While Linkfreeze worked fine when you passed something with ".asp" as part of parameter, Ape instead can't properly parse that. That is a very common parameter when I need to pass a previous page or URL to be redirected to (say for login).

For example.

Standard URL
redirect.asp?page=http://www.somesite.com/newpage.asp

Linkfreeze with dashes (works, just URL-encode that page):
redirect.asp-page-http%3A%2F%2Fwww.somesite.com%2Fnewpage.asp

Helicon Ape won't identify that page (get 404 error), I guess because it sees last ".asp" and regex doesn't work as it used to work in Linkfreeze.

I have that on every page for login and logout at least where page is being passed (you may pass through more than 1 URL for this process so Http Request Referer may not work).

Thanks!

[smilie Profile]

Hello,

Can you please let me know.

Maybe it is possible to also include at least a flag in the mod_linkfreeze config to parse .extension differently, not to assume it is at the end of the URL?

For instance:

somesite.com/page.extension-param1-value1-returnpage-/someurl/newpage.extension

somesite.com/page.asp-param1-value1-returnpage-/someurl/newpage.asp

isn't parsing right in Ape vs. old Linkfreeze. It assumes last .extension (.asp in our case) and whatever is before it as a page name.

It should be parsing:
somesite.com/page.asp?param1=value1&returnpage=/someurl/newpage.asp (and whatever URL encoding happened to last parameter)

The new Linkfreeze assumes all params are in the middle and is expecting this:
somesite.com/page-param1-value1-returnpage-/someurl/newpage.asp.asp

Largest Russian language web portal in USA and its visitors will really appreciate this.

Thanks,

[Yaroslav]

Sorry again for the delay.

As for links not translated on pages, can I have RDP access to that server to check it for issues? There can be a number of reasons why it is not functioning and it will be easier to debug if I have access to the server. Since I understand you are still migrating and this server is not in production yet, can you please send RDP credentials to [email protected]?
As for having extension in the middle of the link, I need to investigate it further however, it seems like IIS built-in request filtering is involved in the situation in the first place. LinkFreeze does not even receives this URL when it is requested because IIS filters it before. I will need to google more about it later.

[smilie Profile]

Thanks,

For some reason I can only post in this forum from one PC, others are blocked. Maybe I exceeded logins.

Server us live, my support is setting up a separate VM on it with the site. I will contact your support shortly with details.

Thank you for reply!