I have a user-supplied filename that could be anything, including path segments and fullset of unicode characters (It's decoded as UTF-8 when supplied by the user.
There seems to be quite a bit of debate about what modern browsers will
except.
my $filename = qq{/some/funny looking/"name that the \\'user' provided'
with a \x{263A} (smile).doc};
How can I pass that back in a Content-Disposition "filename" header escaped
correctly?
--
Bill Moseley
mose...@hank.org
