[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


Mike Lattanzio <mlattanzio at rim.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Add Support for RFC 5987    |Add Support for RFC 5987
                   |(Non-ASCII HTTP Header      |(Non-ASCII HTTP Header
                   |Keys/Values)                |Keys/Values) for filenames




--- Comment #2 from Mike Lattanzio <mlattanzio at rim.com>  2012-04-26 13:28:11 PST ---
(In reply to comment #1)
> This is something network layers need to support, and those are not in WebKit repository. What are you planning to do here?

Okay so looking at it now supporting the rfc everywhere might be a bit much, but the actual bug as it was reported to us refers to this method:

platform/network/HTTPParsers.h defines 
String filenameFromHTTPContentDisposition(const String&); 

It doesn't support "filename*=", for example, we have an HTTP log that basically show us receiving this:

--- other HTTP HEADERS ---
Content-Disposition: attachment; filename*=utf-8'ImportantTradeSecrets.doc
--- other HTTP HEADERS ---

But the filenameFromHTTPContentDisposition method is returning an empty string because it doesn't parse the filename*. Perhaps instead of hunting down every place that this could happen I should just fix this specific method. Thoughts?

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