- From: <bugzilla@jessica.w3.org>
- Date: Sat, 11 Aug 2012 23:35:21 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18529 --- Comment #6 from Arun <arun@mozilla.com> 2012-08-11 23:35:21 UTC --- (In reply to comment #5) > I'd rather not get into the business of enforcing correct mimetypes. That > rabbit hole can go deep once you start considering that different mimetypes > accept different parameters. > > I'd rather just treat the mimetype as an opaque string and forward it to > whatever API that is using the mimetype. So what each API does with mimetypes is actually inconsistent! I think that by throwing, we make it clear what *this* API does and doesn't allow. On the other hand, it does involve parsing mimetype strings; other bugs have been logged showing inconsistency RFC2616. I'd still rather throw, unless you feel strongly that this is too strong (or of course if you feel strongly that this will never be implemented and that the bug mentioned in Comment 4 will be marked WONTFIX :) ) -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 11 August 2012 23:35:24 UTC