02-05-2009 03:58 AM
When trying to debug a problem that was occurring only on my device but not in the simulator I discovered that the simulator or the MDS virtualization layer automatically handles HTTP redirects (the server status is 300 : HTTP_MOVED_TEMP or 301 : HTTP_MOVED_PERM).
In the simulator my HttpConnection object would always get a status of 200 HTTP_OK for URI's that had really been moved elsewhere.
On the device, however, it would get redirect status that my implementation was not set up to handle.
I thought I would post this in case anyone else encounters the same problem.
02-09-2009 02:51 PM
Is your connection on the real BlackBerry handheld also going through the MDS Connection Service of a BlackBerry Enterprise Server? If not, it would be up to your application to handle the redirection. The link below lists the connection routes available on a BlackBerry handheld.
What Is - Different ways to make an HTTP or socket connection
Article Number: DB-00396
02-09-2009 04:22 PM
Does this happen with BIS? What if we make a request and the server returns a 302 and cookies and
other things in the headers? Are these absorbed by RIM servers?
06-16-2009 09:53 AM
As asked above, does BIS-B behave like MDS with respect to redirects, authentication, session cookies, maximum request size? I'm hoping to use BIS-B for my application (still working on ISV membership) to avoid the complication of APNs, but I need a transparent HTTP session. At the moment during development I'm using direct TCP in the simulator. It would be good to know now whether BIS-B will have the same issues as the MDS simulator