BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 06-15-2011, 05:24 AM   #1 (permalink)
New Member
 
Join Date: Jan 2007
Location: Sheffield, UK
Model: 8100
Carrier: o2
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default HTTPS forwarding Problem - BES 5.0.3.31

Please Login to Remove!

Hey all

I've been troubleshooting a problem with our Qlikview server and Blackbery app and I think it's something to do with the BES or at least the MDS but I'm a bit of a n00b where this is concerned.

To explain:

We have a server on our network that runs a Qlikview reporting server. It has a Blackberry app that I'm currently configuring for SSL. Our Blackberrys run off our own BES which forwards traffic through our proxy server and then on to its internal destination.

The problem I'm having is that despite the app being configured to only use SSL the connection that gets to the Qlikview server is standard port 80. Tracking back through the logs it seems the connection from the BES that hits the proxy is port 80 despite the app only using 445. Having been through everything I can with Qlikview support it would appear that the BES seems to be receiving the connection request and forwarding it on as HTTP.

I've checked the MDS Proxy string and it is set as below:

Universal resource locator Description
h t t p ://.* Web
h t t p s://.* SSL

The Details for the https string are:

Proxy item Proxy string Proxy type
PROXY (IPaddress):8080 (IPaddress):8080 PROXY


Is there anything I could be missing or BES logs I should check? I'm stumped!


Edit:

I should add that I can see the connection from the device in the MDAT log coming in as 443.

Last edited by malco : 06-15-2011 at 06:04 AM.
Offline  
Old 06-16-2011, 04:15 AM   #2 (permalink)
New Member
 
Join Date: Jan 2007
Location: Sheffield, UK
Model: 8100
Carrier: o2
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Re: HTTPS forwarding Problem - BES 5.0.3.31

Update

I added in a direct mapping for the internal server "h t t p s://servername.*" and it still went over http to the proxy so I added in "h t t p://servername.*" and it now bypasses the proxy but still hits the other end as port 80. I'm guessing I can amalgamate these into ".*://servername.*"

The internal server is a test server so has a self signed cert and we have untrusted certs set to 'No' on the MDS. Does anyone know if this simply refuse the connection or would it send it through http?
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads for: HTTPS forwarding Problem - BES 5.0.3.31
Thread Thread Starter Forum Replies Last Post
Problem with Migration to BES from Desktop Redirector KelvinThomson RIM Software 1 07-14-2009 04:15 PM
BES users are unable to send attachments Simplicity Trevor BES Admin Corner 0 04-29-2009 06:26 PM
BES Forwarding Mail, but Not Showing on Device cwhite BES Admin Corner 3 04-29-2009 07:24 AM
BENCHMARK your BlackBerry speed! Add your results here! Mark Rejhon General BlackBerry Discussion 271 03-12-2007 09:51 PM
External Sending Problem - Domino 6.5.4 on BES 4.0.4 slygeek BES Admin Corner 0 04-02-2006 10:39 PM





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.