WARNING: This server is unstable and will be retired in the next days. If you want to keep this forum available, please request immediately a migration on the Nabble Support forum. Forums that don't receive any migration request will be deleted forever.

 « Return to Thread: multipart/form-data filename encoding: unicode and special characters

Re: multipart/form-data filename encoding: unicode and special characters

by Evan Jones-5 :: Rate this Message:

| View in Thread

 On May 3, 2012, at 17:09 , Anne van Kesteren wrote:
> Yes. I think we should define multipart/form-data directly in HTML and thereby obsolete http://tools.ietf.org/html/rfc2388 as it is outdated and not maintained.

Right; that would be ideal. Despite the fact that HTML5 references that RFC, browsers don't really follow it.

I would be interested in trying to help with this, but again I would certainly need some guidance from people who know more about the vagaries of how the various browsers encode their form parameters / uploaded file names, and why things got that way. It probably would not be helpful for me to try to draft an update to the spec without getting the right implementers on board.

Evan

--
http://evanjones.ca/

 « Return to Thread: multipart/form-data filename encoding: unicode and special characters