Re: Why firefox is not sending 'filename' parameter for form file parts encoded as specified in rfc2388?

2013-03-11 Thread Boris Zbarsky
On 3/11/13 12:27 PM, Gavin Sharp wrote: 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. Which is the reason for this? The main reason is that it's what Netscape and IE did 12 y

Re: Why firefox is not sending 'filename' parameter for form file parts encoded as specified in rfc2388?

2013-03-11 Thread Gavin Sharp
Re-directing this question to dev-platform. Gavin On Fri, Mar 8, 2013 at 7:13 AM, Jaime Hablutzel Egoavil wrote: > rfc2388 states: > > 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