[Webkit-unassigned] [Bug 84977] Add Support for RFC 5987 (Non-ASCII HTTP Header Keys/Values) for filenames

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=84977





--- Comment #4 from Mike Lattanzio <mlattanzio at rim.com>  2012-04-26 13:57:25 PST ---
(In reply to comment #3)
> I don't know what filenameFromHTTPContentDisposition function is - ports that I work on don't use it. Which ports do use it?
> 
> For the Mac port, file name is generated by network layer, using additional considerations to come up with a proper extension.

Looks like blackberry and qt use it. There's also calls into it from platform/network/curl, and platform/network/soup.


Said another way, I basically created this bug to add support for this part of rfc 6266 (which is mentioned in a comment in the code as it is)

// Allow filename part to start with filename= or filename*=
     filename-parm       = "filename" "=" value
                         | "filename*" "=" ext-value

where an ext-value is defined in RFC 5987 as:

     ext-value     = charset  "'" [ language ] "'" value-chars
                   ; like RFC 2231's <extended-initial-value>
                   ; (see [RFC2231], Section 7)

It also looks like Firefox supports an invalid variation on the spec of the format: 

     ext-value     = charset  "'" value-chars

It is missing the optional language, but with only one of the two mandatory single quote characters.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.