Why firefox is not sending 'filename' parameter for form file parts encoded as specified in rfc2388?
The original local file name may be supplied as well, either as a "filename" parameter either of the "content-disposition: form-data" header or, in the case of multiple files, in a "content-disposition: file" header of the subpart. The sending application MAY supply a file name; if the file name of the sender's operating system is not in US-ASCII, the file name might be approximated, or encoded using the method of RFC 2231.
But firefox is just sending 'filename' parameter encoded with the page encoding or the form accept-charset, this is, it is sending raw UTF-8 or the choosen encoding.
Re: Why firefox is not sending 'filename' parameter for form file parts encoded as specified in rfc2388?
Thank you for inquiring about your issue on Mozilla Support! We appreciate your patience while we find an answer to your issue. At this moment I am escalating this to our advanced troubleshooting team who will assist you further in 24-48 hours.