Welcome to ISAserver.org

Yet another link translation problem

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Yet another link translation problem

Page: [1]

Message

<< Older Topic Newer Topic >>

Yet another link translation problem - 3.Nov.2005 5:24:00 PM

neighbourboy

Posts: 1
Joined: 3.Nov.2005
Status: offline

Hello,

I have an odd translation filter problem. I haven't seen any other problem like mine here and I hope I can describe it effectively.

We are publishing several servers externally and we have several rules, one for each server. The internal domains and servernames are translated to something completely different. Each rule has link translation enabled with something like the following for translation:

'http://foo.internal.com' translated to 'https://server1.external.com'
'http://bar.internal.com' translated to 'https://server2.external.com'
'.internal.com' translated to '.external.com'

Why do we have the '.internal.com' translation in there? Long story, but the Reader's Digest version is because a cookie gets set that way, as the single cookie needs to work for all the websites the user is hitting.

I discovered that the order of the link translation rules is important. The '.internal.com -> .external.com' has to appear last. Otherwise, using the first server as an example, it will get changed from 'http://foo.internal.com' to 'https://foo.external.com' instead of 'https://server1.external.com'

However, when ISA does it's translation automatically for you, it seems that it doesn't really matter what order things are in. The '.internal.com -> .external.com' rule always seems to get applied first.

For example on the rule that publishes 'http://foo.internal.com': 'http://bar.internal.com' gets translated to 'https://server2.external.com' just like it should. But no matter what I do, 'http://foo.internal.com' always gets tranlsated to 'https://foo.external.com' when I have the '.internal.com -> external.com' in the list.

The same is true of the other rule for 'http://bar.internal.com'. The other translations work Ok, but the server for this rule always gets translated to 'https://bar.external.com', instead of 'https://server2.external.com'

If I could somehow turn off the automatic stuff that ISA 2004 does I think that would fix the problem. We didn't have this trouble in ISA 2000.

Does anybody have any ideas? Thanks much and I hope this makes some sense.

--David