15287 2007-09-26 08:51:29 -0700 WebKit does not support non ascii parameters defined in RFC2231 2010-09-17 08:11:58 -0700 1 1 1 Unclassified WebKit New Bugs 523.x (Safari 3) Mac OS X 10.4 CLOSED INVALID InRadar P2 Normal --- 0 nirs webkit-unassigned ap julian.reschke mrowe rpaplin oldest_to_newest 57082 0 nirs 2007-09-26 08:51:29 -0700 WebKit based browsers do not support headers with non-ASCII parameters according to RFC 2231 <http://www.ietf.org/rfc/rfc2231.txt>. This format is supported by Firefox. Related: - http://moinmo.in/MoinMoinBugs/Non_ASCII_attachments_names_corrupted_on_download 57083 1 16398 nirs 2007-09-26 08:56:28 -0700 Created attachment 16398 CGI script demonstrating the problem To reproduce: 1. Install script 2. Access 3. File > Save As Result: file name is download.py Expected: file name should be עברית Another way: 1. Add link to this script in another html document, e.g. <a href="cgi-bin/download.py">download</a> 2. Right click the link and choose "Download linked file" Result: download to file "download.py" Expected: download to file "עברית" Firefox give expected result in both cases. 57085 2 mrowe 2007-09-26 09:20:46 -0700 <rdar://problem/5475999> 57086 3 mrowe 2007-09-26 09:23:43 -0700 The changes required to support this completely need to be implemented at a lower level than WebKit. This work is being tracked by the associated Radar. I'm going to close this bug as INVALID as the issue is not at the WebKit level. Thanks for the bug report. 57098 4 ap 2007-09-26 11:50:37 -0700 See also: rdar://4727992 83957 5 julian.reschke 2008-06-20 02:34:21 -0700 It would be great if somebody could update this bug with information about how work on rdar://4727992 is progressing. 83963 6 mrowe 2008-06-20 03:52:18 -0700 As it is not a WebKit bug it is not appropriate for us to publish information about it in the WebKit bug database. 88612 7 mrowe 2008-08-15 16:54:10 -0700 *** Bug 20407 has been marked as a duplicate of this bug. *** 88619 8 julian.reschke 2008-08-16 02:10:39 -0700 regarding comment 1 and it's attachment... The test case is incorrect. It uses filename*="utf-8'en'%D7%A2%D7%91%D7%A8%D7%99%D7%AA" while it should be filename*=utf-8'en'%D7%A2%D7%91%D7%A8%D7%99%D7%AA according to the "extended-initial-value" production in Section 7 of RFC 2231 (<http://greenbytes.de/tech/webdav/rfc2231.html#rfc.section.7>) 88634 9 22834 nirs 2008-08-16 12:37:43 -0700 Created attachment 22834 Fixed test case This test case does not work with Safari 3.1.2 and Mac OS X 10.4.11, but works with Firefox 2 on same system. 88635 10 ap 2008-08-16 13:26:17 -0700 (In reply to comment #8) > filename*="utf-8'en'%D7%A2%D7%91%D7%A8%D7%99%D7%AA" > filename*=utf-8'en'%D7%A2%D7%91%D7%A8%D7%99%D7%AA AFAICT, these only differ in that the original one has quotation marks. Could you please clarify why they are no allowed? It is strange to me because (1) extended-initial-value is not referenced anywhere else in RFC 2231, so formally speaking, it does not mean anything; and (2) RFC 2231 itself has an example that uses quoted strings: Content-Type: application/x-stuff title*0*=us-ascii'en'This%20is%20even%20more%20 title*1*=%2A%2A%2Afun%2A%2A%2A%20 title*2="isn't it!" Does the variant with quotations marks work in other browsers? 88669 11 julian.reschke 2008-08-17 05:52:29 -0700 > AFAICT, these only differ in that the original one has quotation marks. Yes. > Could you please clarify why they are no allowed? It is strange to me because > (1) extended-initial-value is not referenced anywhere else in RFC 2231, so That's a known erratum, see http://www.rfc-editor.org/errata_search.php?eid=477. > formally speaking, it does not mean anything; and (2) RFC 2231 itself has an > example that uses quoted strings: But not in the initial value. > Does the variant with quotations marks work in other browsers? I'm going to test it, but I'm really not sure why it would matter. The spec is there for a reason. 89169 12 julian.reschke 2008-08-23 09:31:30 -0700 More test cases: <http://greenbytes.de/tech/rfc2231/> Proposed profile for use of RFC2231 encoding in HTTP: <http://greenbytes.de/tech/webdav/draft-reschke-rfc2231-in-http-latest.html> 89835 13 nirs 2008-08-31 19:11:24 -0700 (In reply to comment #12) > More test cases: <http://greenbytes.de/tech/rfc2231/> http://greenbytes.de/tech/tc2231/ 280645 14 julian.reschke 2010-09-17 08:11:58 -0700 In the meantime, draft-reschke-rfc2231-in-http has been published as IETF RFC 5987 on the standards track. 16398 2007-09-26 08:56:28 -0700 2007-09-26 08:56:28 -0700 CGI script demonstrating the problem download.py text/plain 213 nirs IyEvdXNyL2Jpbi9lbnYgcHl0aG9uCiMgfip+IGNvZGluZzogdXRmLTggfip+CgpwcmludCAnJydc ClN0YXR1czogMjAwIE9LCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbgpDb250ZW50LURpc3Bvc2l0 aW9uOiBpbmxpbmU7IGZpbGVuYW1lKj0idXRmLTgnZW4nJUQ3JUEyJUQ3JTkxJUQ3JUE4JUQ3JTk5 JUQ3JUFBIgpDb250ZW50LUxlbmd0aDogMTEKCtei15HXqNeZ16onJycK 22834 2008-08-16 12:37:43 -0700 2008-08-16 12:37:43 -0700 Fixed test case download.py text/plain 201 nirs IyEvdXNyL2Jpbi9lbnYgcHl0aG9uCiMgfip+IGNvZGluZzogdXRmLTggfip+CgpwcmludCAnJydc ClN0YXR1czogMjAwIE9LCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbgpDb250ZW50LURpc3Bvc2l0 aW9uOiBpbmxpbmU7IGZpbGVuYW1lKj11dGYtOCdlbidKJUMzJUJDcmdlbgoKVGhpcyBmaWxlIHNo b3VsZCBiZSBzYXZlZCBhcyBKw7xyZ2VuLgonJycK