You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Max Woghiren (JIRA)" <ji...@apache.org> on 2013/02/21 00:27:14 UTC

[jira] [Commented] (CB-2501) FileUtils.getMimeType(String file) does not work for content:// URIs

    [ https://issues.apache.org/jira/browse/CB-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582655#comment-13582655 ] 

Max Woghiren commented on CB-2501:
----------------------------------

Also, can you clarify for me: are you seeing the mime type issue despite the fix in the duplicate?  Or is that fix the reason why you closed this bug as a duplicate of a fixed bug?

I'll clarify as well: I've chosen to reopen this bug (instead of make a new bug) because you mentioned using ContentResolver.getType, which is what my fix does to remedy the content:// URI case.
                
> FileUtils.getMimeType(String file) does not work for content:// URIs
> --------------------------------------------------------------------
>
>                 Key: CB-2501
>                 URL: https://issues.apache.org/jira/browse/CB-2501
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.2.0
>            Reporter: Christian Kuetbach
>            Assignee: Max Woghiren
>            Priority: Minor
>             Fix For: 2.4.0
>
>
> There is a bug in Android: http://code.google.com/p/android/issues/detail?id=8806
> Because of this the returned mime type will be wrong, if the file extension is not lowercase.
> myImage.jpg -> image/jpg
> myImage.JPG -> null
> I will provide a patch, which simply converts the filepath to lower case, but think there is a better solution than using the MimeTypeMap. The Class ContentResolver has a method getType() 
> http://developer.android.com/reference/android/content/ContentResolver.html#getType(android.net.Uri)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira