Re: None US ASCII characters not allowed in headers?

On Sat, June 9, 2007 2:51 pm, Frank Arensmeier wrote: > I have been struggling with a little problem for quite some time now, > without finding a good solution. > > On one of my pages, users are able to download files that contain > none US ASCII characters in their filenames (e.g. character ö,ä,å). > And I would like to set the original filename in the content header. > But according to RFC2183 on "... The Content-Dispostion Header > Field", characters that are not part of US ASCII are not allowed in > content headers. Is there any chance to get around this limitation? > On the other hand, uploading files that contain "special characters" > in their filenames is no problem. Why is that so? My "solution" so > far is that I simply replace those characters (ä with a, ö with o and > so on). If those characters are valid in URLs, or can be URL-encoded to be valid, then this rant may let you achieve your goal, bypassing the Content-disposition issue(s): http://richardlynch.blogspot.com -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?