I have a internal site requiring HTTPS. For development, I also have the same site running on HTTP. I'm noticing that there is 3-4 time longer wait using HTTPS even when requesting very simple text pages consisting of no more than 300 characters. If I turn the TLS setting to Handheld, the HTTPS site is considerably faster. I'm noticing the issue with more than one Blackberry device.

My understanding is the MDS and dispatcher service that the BlackBerry browser uses is supposed to optimize and encrypt the data exchange.

Our configuration:
BES 4.1.4, BlackBerry browser, 8830 devices v 4.2.2.176

Shouldn't TLS in proxy mode do the opposite - speed up our intranet sites?

After performing some more tests, changing the TLS setting to handheld didn't actually speed up things as much as I originally thought. Rather, it changed how the page appears to load. In proxy mode, the request takes a very long time, and then the page renders fairly quickly. In handheld mode, the total time is about the same, but the page renders much slower. However, I can still verify that HTTP access is much faster. I've re-configured our testing webserver and both HTTPS and HTTP.

I've found some diagrams that made the different settings on the handheld much more clear to me.
How to Access Corporate Data with BlackBerry -- This white paper from Research In Motion details how to use BlackBerry to extend enterprise information wirelessly. ++ Tags: Application Development, Authentication, Business Solution, Business Technolo

So, it appears that if your website is HTTPS, it's encrypted with 3 layers. Two with SSL and one with triple DES. Does this sound accurate?

Is anyone else experiencing low performance on internal HTTPS sites?