How do I overcome the fact that not all HTTP requests require redirection

[Richard Bradfield]

                   I have the following scenario, The Business require that the main login to JDE is just http://prod.apps, I use a redirect server to change it to

http://prod.apps:12001/prod/Mainmanu.maf  so that all works well , but reports and approvals generate links with URIs so the redirect does not work. To overcome this problem I have generated another context with a different VIP without a redirect server and that seems to work ok. But the apllication programmers have to ensure that any reports etc point to this new VIP.

Is there a better  way of doing this?

[Borys Berlog · Accepted solution]

Hi

You may  use L7 http class map and add additional matching by GET field in url request (as one possibility). E.g.

currently you have something like this :

policy-map type load first NAME

class class-default

serverfarm

you may add something like this :

class type http load match-any

match http url

then your L7 map will look like :

policy-map type load first NAME

class

serverfarm

class class-default

serverfarm

More information you can find here :

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA4_2_0/configuration/slb/guide/classlb.html#wp1021430

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA4_2_0/configuration/slb/guide/classlb.html#wp1021388

I think it should allow you to have only one VIP for this application. Please try - if you don't succeed, please post URL you use to access reports/approvals links.

If this answer resolved your problem - please mark it as correct it will help to keep our forum more organized.

Thank you.

[Richard Bradfield]

Borys,

looks like you got me on the right track, The business just wanted to have a simple link to JDE,

I'll have a play with a test setup later, and let you know how I go

thanks for your help

[Richard Bradfield]

Borys, thanks for your help seems to be working ok, thoughIi will need to do further testing before goes into the production Context.

I do get the following system log messages though when I connect

%ACE-3-400001 MSS mismatch from 172.16.5.185:12001 (1460) to 172.16.10.25:49591(1260) on interface vlan171

I am running A4(2.1) on the ACE and there is a fix in later releases for this, also I am conecting thru a VPN so that might mean the MSS is less on the client. I see what it is like when I am in the office tomorrow.