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

[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 years ago, so 
servers were written to expect it, so other browsers had to copy it, so 
more servers were written to expect it  and here we are.


-Boris

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

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

[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 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.
>
> Which is the reason for this?
>
> --
> Jaime Hablutzel -  RPC 987608463
> ___
> dev-apps-firefox mailing list
> dev-apps-fire...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-apps-firefox
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform