Sorry, this got sent too quickly:
On Wed, Feb 29, 2012 at 2:15 PM, Bill Moseley <mose...@hank.org> wrote:
> 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?
>
And does $request->header( $name => $value )
expect $name and $value to be Character data (decoded into Perl characters)
or does it always need to be encoded first? Seems like the encoding should
happen when the request gets "rendered" for output.
--
Bill Moseley
mose...@hank.org
