Miles Crawford wrote:
I agree it looks bogus, but safari and firefox send the header in that
format. Not sure about IE since Windows does not allow files with a "
in the name.
I looked over the Content-Disposition header RFC but it does not seem
to address escaping directly.
Either way, it seems that this format is a "browser fact of life"
I suggested this in IRC, but never saw a reply. Perhaps it's because
you're using $r->param for a input type=file? I'd check to see what
$upload->filename gives you when you use Apache2::Upload to handle the
file upload instead.
Adam
