server_data workflow - what am I doing wrong?

If I read this right, then you're intentionally sending multiple HTTP responses (with the encapsulated screen data) for a single request? I'm surprised that the clients' HTTP proxy/firewall allows this at all, and I'm even more surprised that it breaks when the multiple HTTP responses are contained in the same packet (which is completely legal). I'd first make sure that this really is what the situation is by crafting some test programs and not use the BIG-IP or ESX server at all.

 

 

If that is the real situation, I can come up with 2 ideas to maybe solve this problem:

 

1) For the screen refresh data, use the CONNECT method through the clients' HTTPS proxy, which would simplify the iRule greatly.

 

2) If the server really always sends responses only in single packets, then you should be able to minimally parse the responses to bundle up all of the screen data into a single HTTP response.

 

 

Also, depending on the precise nature of the clients' proxy/firewall, a series of 100 responses might be more readily accepted than a series of 200 responses. You might also need the appropriate Expect header on the client request. Just some thoughts...