images irule

Each HTTP object, even images referenced within an HTML page, is a separate request, and each request can be sent to a different pool using logic similar to yours. It sounds like you need to be able to tell when an image is called by /branch.html. You can tell what page called the images by examining the "Referrer" header -- something to consider in building your conditions.

 

 

Adding log statements such as "condtion X seen, using pool Y" can help reveal where your rule logic is broken, if that is indeed the case.

 

 

But I could see how sending request to 2 different servers could interfere with jsessionid assignment such that one server's sessionID would overwrite the other's.

 

 

Can you make the image servers stop generating a 2nd jsessionid? If it's just serving images, I would think the server doesn't need to create stateful sessions.

 

 

If you can't prevent the 2nd sessionID from being set, in v9 you could intercept the 2nd jsessionid from the image server if the request came from that Referrer, and delete that cookie.

 

 

HTH

 

/d