[Boo-meringue]

I've wiped and reactivated a 9000 handset that I'm using for testing and sadly the problem is still the same.

We use bluecoat for corporate web filtering, not sure if that might have a bearing on this.

[MisterGriffiths]

Have you got 'Scalable Sockets' and 'Use Scalable HTTP' enabled?

[Boo-meringue]

I disabled those as per freakinvibe's advice on the last page. It fixed some intermittent HTTP errors I was getting but not the missing images.

[MisterGriffiths]

Sorry missed that.

[Boo-meringue]

So tomorrow we're hopefully going to allow our BES direct access to the internet so we can test browsing without the proxy. It's been a pain in the **** to organise this as any firewall changes need to go through our lengthy change control process, even just for testing. Our carrier's support have said it's a step we need to take.

I fully expect it to resolve the problem, not really sure how that knowledge is going to help though!

[Belone]

Further to this (OP is on leave at the moment so I'm picking up in his stead). I've discovered this seems to only actually be affecting Blackberrys on OS versions below 6.

I have noticed in version 6 RIM replaced the "Show Images" option in Browser Configuration with "Load Images". One would assume this is purely a name change rather than a change to functionality, though obviously changing the option to off makes the web pages appear as they do on version 5 and below.

Since this only started occurring after we updated the BES to 5.03 MR7 from MR4, I'm wondering if anyone knows if there is perhaps a compatibility issue with older handsets - though since no one else seems to have come across this it seems unlikely.

Any further help would be greatly appreciated.

Thanks.

[freakinvibe]

With OS 6, RIM completely re-vamped the browser. This completely new browser is based on WebKit and has nothing to do with the old browser, so it is well possible that options and behaviour changed. Still, pictures should be visible also on the old browser.

[Boo-meringue]

O2 are now referring this issue over to RIM (hooray!). We've supplied them with a lot of information and testing data, I hope RIM can get to the bottom of this! I'll post back here if and when we get a result.

[Boo-meringue]

Solved.

KB29850-Images are not displayed when browsing via BlackBerry Mobile Data System Connection Service routing through a HTTP proxy

RIM made a change to HTTP transcoding from MR6 onwards. Using workaround 2 in that Knowledgebase article resolved the problem immediately.

For this workaround you need to an older (pre-MR6) version of a file called transcoderHTML.jar.

To get this file:

1. Go into the original install folder for BES 5.0.3 (C:\BlackBerry\BES 5.0.3 Full\besx_5.0.3\bundle0033 on our BES - I think this is the default path)
2. Find the file called MDSCS.cab and open it
3. Within the cab file find the file called File_22_40_transcoderHTML.jar.C60727D2_6BDE_4F06_B 932_CA2A75909E6B and extract it
4. Rename the extracted file to transcoderHTML.jar

You can then follow the instructions in the KB article to replace the newer file.

[knottyrope]

not a fun ordeal, but glad you stuck with it

[hapklaar]

Sad to see it effects MR8 as well. Does anyone know if it makes a difference when I use the transcoderHTML.jar from the 5.0.3 install or the MR5 version?