-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Todd Pattist wrote: > I'll answer my own question for the record. > > It's the Content-Disposition: attachment; filename*=UTF-8''filename.zip > header that causes the problem. I set wget to use the Privoxy proxy > (wgetrc line): > > http_proxy = localhost:8118/ > > and then set Privoxy to modify incoming server headers with a Privoxy > filter:
Of course, many are not so fortunate to be able to use-and-configure a proxy in order to solve such problems. Astonishingly, I've never come across this syntax before. It appears to be documented in RFC 2184, from back in 1997 (for MIME headers, which technically aren't precisely the same as HTTP headers; but then, Content-Disposition itself is a MIME header, and not an HTTP header, so...). I'll file an issue for Wget to handle this in the future, though I'm not sure how soon it'll be in. Part of it probably depends on how frequently this syntax appears in the wild. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1Wi97M8hyUobTrERAgYJAJ9kmEuRKjNtEF2H3BEw4K2rm6Ci0QCfQgmz gYam097P0f2xxsgoCOys71s= =xlTH -----END PGP SIGNATURE-----
