Tim wrote:
> There's no good way to handle that. It's the generic description for
> any binary file (sound, picture, PDF, whatever), that hasn't been
> specifically identified. If you were to hard-configure it to presume
> PDF, it'd fail on the next thing that wasn't a PDF but described as
> being octet-stream.
They could figure out the MIME type client side using the same shared-mime-
info-based mechanisms which are used after saving the file (extension,
sometimes file contents), either just for generic application/octet-stream
attachments or generally ignoring the sent MIME type.
Kevin Kofler
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
