[aylnews]

We've used a scheduled script to generate a "Browser-Message" to push an HTML table of data to a group of BlackBerries via an MDS server. The HTML is dynamically generated; it doesn't exist at any URL and so we pass a "Content-Location" header that points to the root of our intranet because not passing one resulted in the "Browser-Message" not being sent and yet passing our intranet home URL seems to work fine.

The “Browser-Message” API documentation suggests that the content of the POST message will appear in the Inbox on a BlackBerry device and be displayed verbatim when clicked. If the user subsequently chooses the “Refresh” menu option, the BlackBerry device will visit the URL passed in the “Content-Location”, download fresh content and display it.

Seemingly in OS5 this was how it worked for us. As I understand it, the Browser–Message needn’t be html, it may just be a short text note so whether it’s rendered by the MDS Browser or BlackBerry Browser shouldn’t make a great deal of difference for simple content.

However, OS6 seems to ignore the POSTed content and downloads the content directly from the URL passed in the “Content-Location” HTTP header. Whilst this might be OK if the Browser-Message content exists at that URL, if it’s dynamically generated on–the–fly it may be necessary to pass an alternate URL in the “Content-Location” HTTP header but certainly isn’t what the BlackBerry device should be displaying first of all. It should display the content of the POSTed message.

I have attached the test vbs script which works fine for OS5 but not on OS6.

I have contacted RIM and opened a case and after much back and forth they have decided it was not a problem but a developer issue and we then had to log a case with the RIM developers which then incurs a fee.

Any help or suggestions would be greatly appreciated.

[dc/dc]

You need to look in the BES Admin Corner.

[aylnews]

I have now posted this in the BES Admin Corner. Thanks for your help.

[hrbuckley]

It has been a while since I did any development work with pushing message through the BES. But IIRC the push never guaranteed the the content of the message would be available when the user looks at it. One of the reasons is the memory could be turned over to something else if needed and only the URL retained so it may be fetched later.