Forum Discussion
rb1980_75708
Nimbostratus
Nimbostratusmuticonnect across applications?
I was trying to play around with the multiconnect feature in WA and am not understanding the logic of how it might work across multiple applications. I will try and simplify my example:
Let's say I have 2 applications running on the WA: each with their own application, classes and policies.
There is an "images" application that is tuned for serving images on the hostname images.domain.com.
There is a "www" application that serves web pages for the hostname www.domain.com. In that app there is a page called pagewithlotsofimages.html that contains a bunch of img src= links to images that are served by the host images.domain.com (which is served by the other application).
Here's where i'm confused:
If I enable the multiconnect feature in the www policy for the page pagewithlotsofimages.html I then have to go into the "images" application and enable the subdomains under the multiconnect options there so that it generates waNN.images.domain.com?
What if there are links on that same page that are NOT served from images.domain.com? What will happen to them?
My hunch tells me that the multiconnect feature will not work this way: that it will only work within a single application/hostname.
- Interesting deployment. If I understand the configuration you should be fine - of course I highly recommend testing to make sure what I say works properly. MultiConnect is controlled by both the policy and the application. If application 1 has MC subdomains configured then the base HTML will be re-written to wa1.images.domain.com. If application 2 does not have MC subdomains configured then the base HTML will not be re-written so even though the images are served from the same domain the client will not see the wa1.images.domain.com in the HTML.
rb1980_75708hmm... I guess I still don't understand conceptually how this would work. I guess i'll just have to try it and see.
But to my previous question, will all of the image links get rewritten, even ones that don't point to images.domain.com, or is it smart enough to figure that out?
