For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

fillstrsoh_2962's avatar
fillstrsoh_2962
Icon for Nimbostratus rankNimbostratus
Oct 26, 2011

SharePoint 2010 - virtual with two pools

We are trying to implement SharePoint 2010 using one virtual server with two pools using a pool for each site. dv-strsohioportal is the virtual server which has an irule that sends traffic to a specif...
config
design
Kurt_Knochner_5's avatar
Kurt_Knochner_5
Icon for Cirrus rankCirrus
Oct 31, 2011
O.K. now I'm a bit cinfused. You are rewrting the external URI dv-strsohioportal.tld to paris-test.tld and you distribute the requests to two different sites (/inv and /its). Is that correct? If so, why is your internal domain (paris-test.tld) different that your external (dv-strsohioportal.tld)? In that case you'll have to rewrite the Host Header as well. Furthermore you should also use a STREAM profile to rewrite any occurances of paris-test in the HTML code to dv-strsohioportal, otherwise some absolute links might not work, as the external client does not know how to access http://paris-test.tld.

 

 

TODO:

 

 

1.) Rewrite the HOST Header [HTTP::header Host]

 

2.) Add a STREAM profile to rewrite HTML

 

3.) Don't add /default.aspx to every page. Change

 

 

this: HTTP::uri "http://paris-test[HTTP::uri]/default.aspx"

 

to this: HTTP::uri "http://paris-test[HTTP::uri]

 

 

Hope that works. If it does not, I reccommend to capture the whole traffic between client -> LB -> backend with tcpdump and check where rewriting works and where not.

 

 

BTW: paris-test is not a FQDN. Is that just to obfusciate the domain name? If not, how does the LB resolve that name and how does the webserver handle that "domain name"?

 

 

Regards

 

Kurt Knochner