Forum Discussion
Brad_146558
May 14, 2015Nimbostratus
The issue turned out to be certificate related oddly enough. It seemed there was something about the PKCS12 certificate that the integrated mobile browser didn't like when it was published through the F5. What made this hard to find is no one was looking at the certificate because we never saw any certificate related errors and the issue never happened while using traditional desktop browsers.