Red Hat Bugzilla – Bug 618713
attachment type autodetection does not work for some files
Last modified: 2015-05-04 21:20:36 EDT
Description of problem:
When I attach for example file.log of file.patch and I leave option autodetect selected, the attachment type is always "application/octet-stream".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. attach file.patch and select "autodetect type"
2. observe the attachment type
text/plain (with patch checkbox checked)
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can.
Bugzilla Development Team
Note that the MIME type is set by your web browser, not by Bugzilla itself.
Created attachment 585752 [details]
(In reply to comment #2)
> Note that the MIME type is set by your web browser, not by Bugzilla itself.
What??? So after six years inability to fix this well known bug, you started to blame browser?
Steps to reproduction:
1. Take a plain text file (like the attached one)
2. Leave the MIME type to "auto-detect"
3. Click Submit.
for at least 8 times out of 10 the MIME type is set to application/octet-stream (which means I cannot read the attachment in browser, but it downloads)
it should be set to text/* (and ALL text/* should be opened in browser, but that's another bug)
(In reply to bug 555677 comment 5)
> The MIME type is set by your web browser, not by Bugzilla itself. This means
> that your browser didn't detect your file as text/plain, but as text/x-log.
When I open this file in browser from file:///tmp/Xorg.0.log and press Ctrl-I it says the file is text/plain.
*** Bug 573036 has been marked as a duplicate of this bug. ***
*** Bug 555677 has been marked as a duplicate of this bug. ***
(In reply to comment #3)
> What??? So after six years inability to fix this well known bug, you started
> to blame browser?
I blame the one which sets the MIME type, which is your browser, yes. If you want Bugzilla to correctly fix the MIME type itself, you should use the typesniffer extension, see http://bzr.mozilla.org/bugzilla/extensions/typesniffer/trunk/files.
(In reply to comment #7)
> I blame the one which sets the MIME type, which is your browser, yes. If you
> want Bugzilla to correctly fix the MIME type itself, you should use the
> typesniffer extension, see
*I* should? These are bugzilla extensions, aren't they? So we should use them on bugzilla.r.c instance, shouldn't we?
Please do something about this at the _bugzilla_ end -- I'm not worried about setting the MIME type for the files I _upload_. I'm trying to avoid having to manually change the MIME type for every attachment I want to view that someone _else_ uploaded...
We'll inherit the change when we migrate to Bugzilla 4.4
Committing to: bzr+ssh://firstname.lastname@example.org/bugzilla/trunk/
Committed revision 8284.