Archived:Content-Disposition header ignored in some S60 3rd Edition devices
The web browser and Web Runtime ignore the Content-Disposition header received with the HTTP response in some S60 3rd Edition devices.
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.
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.
Currently no solution exists.