(In reply to Dennis Schubert [:denschub] from comment #10) > (In reply to :Gijs (he/him) from comment #8) > > Is it? > > This is, afaict, essentially, the same as bug 1875646, except that that one is a 7z and this one is a pkg. So both issues are site reports about the same underlying platform difference. This would still need a platform bug what we can block bug 1886142 against. There was a bit of added context in the triage meeting we just had, that it's bad not to have a platform issue filed for this, but of course I didn't note that in the comment. OK, fwiw, I didn't re-read 1875646 before my previous comment, but that bug has the server send no `content-type` at all, whereas here the server explicitly sends `text/plain` (which is obviously wrong). So it's not quite the same bug; the mimesniff spec has considerably more leeway for interpreting a content type in the former case than in the latter. Anyway, I filed bug 1896460.
Bug 1892582 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Dennis Schubert [:denschub] from comment #10) > (In reply to :Gijs (he/him) from comment #8) > > Is it? > > This is, afaict, essentially, the same as bug 1875646, except that that one is a 7z and this one is a pkg. So both issues are site reports about the same underlying platform difference. This would still need a platform bug what we can block bug 1886142 against. There was a bit of added context in the triage meeting we just had, that it's bad not to have a platform issue filed for this, but of course I didn't note that in the comment. ~OK, fwiw, I didn't re-read 1875646 before my previous comment, but that bug has the server send no `content-type` at all, whereas here the server explicitly sends `text/plain` (which is obviously wrong). So it's not quite the same bug; the mimesniff spec has considerably more leeway for interpreting a content type in the former case than in the latter.~ Edit: Argh, I made the same mistake as when I originally responded to that bug! That's embarrassing. Anyway, I filed bug 1896460.