09-15-2009 05:26 PM
The company I work for (Mogreet.com) delivers video to handsets via SMS and MMS.
We are experiencing a problem related to content length when delivering to balckberry devices specifically on BES, where the allowed content size is set too low for our use. Apparently the default http connection size is 128k.
the error the handset reports is:
HTTP Error 413: Request Entity Too Large
In any case, if I could identify from the handset uaprof or any other header that this device was on a BES, I could make sure that the content we serve to that handset was under 128k.
Does anyone know of a way to tell from the handset http headers whether a device hitting a web server is on BES or not?
I appreciate any insight.
Below is a representative set of headers from a blackberry on a BES.
HTTP_ACCEPT : text/html,application/xhtml+xml,application/vnd.wa
HTTP_ACCEPT_CHARSET : ISO-8859-1,UTF-8,US-ASCII,UTF-16BE,windows-1252,UT
HTTP_ACCEPT_LANGUAGE : en-US,en;q=0.5<br>
HTTP_USER_AGENT : BlackBerry9000/18.104.22.168 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/102 UP.Link/22.214.171.124.06.3.1.20.0<br>
HTTP_X_WAP_PROFILE : "http://www.blackberry.net/go/mobile/profiles/uapro
HTTP_X_UP_DEVCAP_SMARTDIALING : 1<br>
HTTP_X_UP_DEVCAP_ISCOLOR : 1<br>
HTTP_X_UP_DEVCAP_SCREENDEPTH : 16<br>
HTTP_X_UP_DEVCAP_CHARSET : ISO-8859-1,UTF-8,UTF-16BE,UTF-16LE,windows-1250,wi
HTTP_X_UP_DEVCAP_SCREENPIXELS : 480,320<br>
HTTP_X_UP_DEVCAP_ACCEPT_LANGUAGE : de,en,es,fr,it,pt<br>
HTTP_X_UP_SUBNO : T_PAC_LAX_1238373087000105556823<br>
HTTP_VIA : 1.1 bthmagr1fe04WAP2-mbl<br>
HTTP_X_FORWARDED_FOR : 126.96.36.199<br>
HTTP_CONNECTION : Keep-Alive<br>
I see this differing on another handset:
HTTP_VIA : BISB_188.8.131.52, 1.1 pmds358.bisb1.blackberry:3128 (squid/2.7.STABLE6)<br>
Could the http_via header tell me whether it's on a BES?
thanks in advance!
I'm rockin the BlackBerry PRIV, Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook,BT Headset HS-700
09-15-2009 08:31 PM
pmds358.bisb1.blackberry could be using MDS on a BES.
WAP is just going through the carrier, but could still be using a BES server but the browser is using WAP instead.
Then there is the WiFi browser but the device could still be on a BES.
There are 3 browsers it can use.
I think the BB Browser is the one that your being affected by.
this thread might be better known as
How to detect handset**bleep**ting a web server going through BES v.s. Not going through BES ?
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V