11-22-2012 11:20 AM
This used to work but for some reason we can no longer access any https sites via the MDS browser. When we access https://mobile.twitter.com for instance you get the message "Bad request mobile.twitter.com:443"
Access is ok when attempted from the BES itself logged in as the user account that is configured in the MDS connection proxy mappings.
We had this problem after updating to BES 5 SP4 but it was fixed by adding an entry in the proxy mappings to force anything starting with https:// to our proxy. There was already a rule forcing everything to the proxy but for some reason this additional rule was necessary.
Is there anything I can try/check?
Solved! Go to Solution.
11-22-2012 03:53 PM
We had the same issue when we upgraded to SP2. Have you checked:
On the other hand, SP3 introduces another problem: Known issues:
If you set the Use Scalable HTTP option to No, users can no longer browse to HTTPS web sites. (DT 1049666)
Workaround: Set Use Scalable HTTP to Yes and restart the BlackBerry MDS Connection Service.
When a BlackBerry device user accesses an untrusted web site using BlackBerry® Device Software 5.0 or BlackBerry® 6, the device displays the "HTTP Error 400: Bad Request" error message. (DT 1029071)
Workaround: In the BlackBerry Administration Service, set the Use Scalable HTTP option to Yes.
These issues should be sorted with SP3 MR3. I don't know what the status with SP4 is.
Try to play around with the Scalable HTTP setting and the TLS Trusted server list.
11-23-2012 04:00 AM
Thanks for that. It has made a difference but maybe just to flag up another problem. The error has now changed to "Only basic authenticated HTTPS proxy server is supported"
11-23-2012 06:04 AM
So how are you authenticating to the proxy (Basic, NTLM, Kerberos)? Could you make an exception for the BES server, so it does not need authentication to the proxy?