25894 2014-05-27 15:37:59 +0000 "The parts of the generated multipart/form-data resource that correspond to non-file fields must not [...] 2014-05-28 09:23:36 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#multipart-form-data P3 normal Unsorted 1 contributor ian ian mike w3 contributor oldest_to_newest 106845 0 contributor 2014-05-27 15:37:59 +0000 Specification: http://www.whatwg.org/ Multipage: http://www.whatwg.org/C#multipart-form-data Complete: http://www.whatwg.org/c#multipart-form-data Referrer: http://www.whatwg.org/ Comment: "The parts of the generated multipart/form-data resource that correspond to non-file fields must not have a Content-Type header specified. " THIS IS SO FUCKING WRONG, HOW THE FUCK IS THE SERVER SUPPOSED TO KNOW THE FUCKING ENCODING YOU SHITTARDS??? BECAUSE OF THIS SHIT FIREFOX DOES NOT GIVE ANY FUCKING INDICATION AS TO WHAT THE FUCKING ENCODING OF THE FUCKING FORM DATA MIGHT BE WHEN POSTING MULTIPART FORMS. RESTEASY WHICH CONFORMS TO THE FUCKING SPEC THEN DECODES EVERYTHING AS ASCII DO YOU KNOW HOW MUCH FUN I AM HAVING WRITING THIS FUCKING WEBAPP FOR SUBMITTING TRANSLATIONS RIGHT NOW????? I WILL UNIRONICALLY MURDER THE SACK OF SHIT THAT PROPOSED OMITTING THE FUCKING PIECE OF INFORMATION THAT WOULD HAVE ALLOWED THE SERVER TO DECODE THE MOTHER F U C K I N G REQUEST ARARAHRHAHRUHEURHEAUHUEHRUAHUTHUHUTH Posted from: 80.66.100.2 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 106858 1 ian 2014-05-27 21:43:55 +0000 Use the magic _charset_ field if you want the character encoding. Note that the specification was not written by the person who designed this feature. The specification just reverse-engineered what was already implemented. 106903 2 w3 2014-05-28 09:23:36 +0000 I don't want to start the millionth charset discussion (I've given up), but let me tell you: When I punched the above all-uppercase text into that feedback box, I didn't expect a) it would be converted into a bugzilla issue b) someone would (have to) read it and least of all, c) a sincere reply. Sorry you had to deal with this... sorry I have to deal with HTML.