Archived:Content-Disposition header ignored in some S60 3rd Edition devices

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Tested with

Devices(s): Nokia N95 8GB

---

Compatibility

Platform(s): S60 3rd Edition, FP1

---

Article

Created: User:Kbwiki (30 Jun 2009)

Last edited: lpvalente (20 Sep 2012)

Overview

The web browser and Web Runtime ignore the Content-Disposition header received with the HTTP response in some S60 3rd Edition devices.

Description

According to RFC 2183, if the disposition-type is attachment, then the display of the content "should not be automatic, but contingent upon some further action of the user". In other words, the user should be prompted what to do with the content (open, save, etc).

It seems that the browser always opens the content inline, which is problematic in the case of binary files that have no matching handlers (recognizers) on the platform, resulting in gibberish shown to the user.

How to reproduce

Craft a web component that provides the appropriate response headers to duplicate the issue.

For example: http://www.drivingrecorder.com/ds/downloads/download_bin.php?file=try.xcf

Opening the URL above in the browser will display the content inline. You can use a network sniffer to see that the Content-Disposition header instructs the browser to handle the content as an attachment, but the browser ignores that, hence being non-compliant with the standards.

Solution

Currently no solution exists.