04-21-2009 07:41 AM
We're unable to view Excel documents when they are **downloaded over https**. The same file is fine when sent as an attachment or downloaded over http, but downloading over https produces a message: "The item you selected cannot be displayed. Do you wish to save the item?". If you click "No", it says "Unsupported media type: application/vnd.ms-excel". Of course, that is the same MIME type sent when downloading over http, and it works just fine.
- Some devices work, some not. 8100 on Verizon fine, 8100 on T-Mobile not, 7100i on Nextel is fine, others on Verizon not.
- Downloads to desktop browsers work fine (just to confirm the file is serving properly).
- Using OS 4.5 on all devices, afaik. Certainly using 4.5 on the 8100 that does *not* work.
- All devices download and show Excel over http fine, so there is definitely software to display the file type.
- Serving very simple Excel-generated file from Apache; there's no custom software involved.
- Using a good SSL certificate on the server that generates no warnings on the BB or any of the desktop browsers.
I'm not sure this is a browser issue, but since it's dependent on how the file is downloaded, my best guess is some configuration in the browser.
10-07-2009 10:01 AM
We have exactly the same issue, fine over http, but not over https.
Im certain it isnt an issue with docs to go, as ive removed it from the HH
Anyone found a workaround to this?
11-12-2009 03:46 PM
I'm having the same issue as well. Here's what I think the problem is:
For a lot of older Blackberries, complex files like pdf, xls, doc etc. get converted into some intermediate, pre-digested format by the BES so that they can be downloaded and displayed quickly on older, slower blackberry devices. So the flow looks like
blackberry --- <sends request> ---> BES ----- <resends request> ----> your server
the above is fine. The problem comes with the response.
your server -----> <sends response with pdf file> ----> BES (if encrypted, do nothing. if not encrypted translate pdf, doc, xls etc. to middle format) ---- <resends response> ------> blackberry (renders if file has been translated, otherwise popup an error message)
I can't really think of a workaround to this except to transmit the content in the clear so it can be translated by the BES.
Any other ideas?
(some heartening news: one of the employees at the developer conference this week showed off one of the new 9700's. He didn't have this issue. So, as older phones get phased out, this issue will disappear...)