Databases
StackOverflow2013
Postsdbo
POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
    primarykey
    data
    text
    <p>I have some legacy code I am dealing with (so no I can't just use a URL with an encoded filename component) that allows a user to download a file from our website. Since our filenames are often in many different languages they are all stored as UTF-8. I wrote some code to handle the RFC5987 conversion to a proper filename* parameter. This works great until I have a filename with non-ascii characters <strong>and</strong> spaces. Per RFC, the space character is not part of attr_char so it gets encoded as %20. I have new versions of Chrome as well as Firefox and they are all converting to %20 to + on download. I have tried not encoding the space and putting the encoded filename in quotes and get the same result. I have sniffed the response coming from the server to verify that the servlet container wasn't mucking with my headers and they look correct to me. The RFC even has examples that contain %20. Am I missing something, or do all of these browsers have a bug related to this?</p> <p>Many thanks in advance. The code I use to encode the filename is below.</p> <p>Peter</p> <pre><code>public static boolean bcsrch(final char[] chars, final char c) { final int len = chars.length; int base = 0; int last = len - 1; /* Last element in table */ int p; while (last &gt;= base) { p = base + ((last - base) &gt;&gt; 1); if (c == chars[p]) return true; /* Key found */ else if (c &lt; chars[p]) last = p - 1; else base = p + 1; } return false; /* Key not found */ } public static String rfc5987_encode(final String s) { final int len = s.length(); final StringBuilder sb = new StringBuilder(len &lt;&lt; 1); final char[] digits = {'0','1','2','3','4','5','6','7','8','9','A','B','C','D','E','F'}; final char[] attr_char = {'!','#','$','&amp;','\'','+','-','.','0','1','2','3','4','5','6','7','8','9','A','B','C','D','E','F','G','H','I','J','K','L','M','N','O','P','Q','R','S','T','U','V','W','X','Y','Z','^','_','a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z','|', '~'}; for (int i = 0; i &lt; len; ++i) { final char c = s.charAt(i); if (bcsrch(attr_char, c)) sb.append(c); else { final char[] encoded = {'%', 0, 0}; encoded[1] = digits[0x0f &amp; (c &gt;&gt;&gt; 4)]; encoded[2] = digits[c &amp; 0x0f]; sb.append(encoded); } } return sb.toString(); } </code></pre> <p><strong>Update</strong></p> <p>Here is a screen shot of the download dialog I get for a file with Chinese characters with spaces as mentioned in my comment.</p> <p><img src="https://i.stack.imgur.com/nOpcA.jpg" alt="screen cap of download dialog"></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeter Friend
    1. USPeter Friend
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
      1. USSimon Michael
      1. VTFavorite
    1. COHere is a sample header that is causing this issue: Content-Disposition:attachment; filename*=UTF-8''Museum%20%5A%69%86.jpg
      singulars
      1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
      1. USPeter Friend
    2. COSee http://greenbytes.de/tech/tc2231/#attwithquotedsemicolon - that test case has a space character in a quoted-string and appears to work in Firefox. Are we testing different things?
      singulars
      1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
      1. USJulian Reschke
    3. COThat looks like something else. That test checks for semicolon within a quoted string. My problem is that I have a filename with Chinese characters as well as spaces, so I am using the filename* form, and in token not quoted form since I read some docs that recommended not using quotes with % escapes. With the example from my comment above the Chinese characters are recognized and converted properly, but the %20 is getting mapped to +.
      singulars
      1. POhandling filename* parameters with spaces via RFC 5987 results in '+' in filenames
      1. USPeter Friend
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload