Application Web Pages Not Being Served Correctly by F5

May I know any update of the solutions on this post? [https://devcentral.f5.com/questions/application-web-pages-not-being-served-correctly-by-f5?lc=1] I am also facing the same issue here and desperately looking for a solution. Error Description: When our web application (.NET 3.5) is accessed through F5 LB with https, we always intermittently hit the error of "sys is not defined". This error will NOT occur if we access the web application via the web server URL directly. That is why I suspect it is due to F5 LB configurations.

NOTE: I am not an F5 expert, and this is the first time I encounter a client using F5 LB.

Architecture background: This project has 1 F5 LB in front, behind F5 there are 2 Web server as reversed proxy and 2 application servers which are actually hosting the web application. The SSL cert is bind in the F5 LB.

Troubleshooting work done and findings so far:

1. The LB and servers are own by the client, and we have no access to the F5 LB. We have asked the client infra guy to ensure the sticky session in F5.

    

2. In the application servers, we have already install .NET Ajax Toolkit 1.0.

    

3. We have tried to disable compression for scriptResource.axd, but the problem remains.

    

4. My colleague uses Fiddler to troubleshoot the problem (unfortunately I couldn't go to client site with her today), and she discovered that the axd file is downloaded to the client browser successfully, but the browser cache value suddenly changed after some time. Details: When the browser cache is empty and the browser first time loads the axd file, everything work normally, she could see the axd file value from the cache, say "APPLE"; then she kept testing the web application again and again until the error occur, after that she checked the axd file in browser cache, it shows a wrong data, meaning "APPLE" now becomes "ADDLE". Then she cleared the cache, the browser retrieves the axd file again and the axd value becomes "APPLE" again, and the program ran fine again. Because of this finding, the client concludes that it is the browser issue not the F5 LB issue. But my point is that our web application has no error in all other test scenarios, only encounter error when it is accessed through F5 HTTPS, WHY?! And I don't believe a browser will change the cache value itself.

    

I am not an infra expert but a software programmer. And I have never encountered such a weird issue with other brands of LB before. Can any F5 expert here give me some advice? Or do you have any F5 contact in Singapore? I would like to contact the expert ASAP. Many thanks.