Message102976
According to RFC2231 the named disposition (content disposition field) is provided by the MIME mechanism. The encoded parameter like the following:
Content-Disposition: inline;
filename*0="Re: [Mailman-Users] Messages shunted with \"TypeError: ";
filename*1="decodingUnicode is not supported\".eml"
is not behaving the way it should be.
The patch by rcoyner seems fine to me as it rectifies the wrong behaviour of _parseparam i.e. the counting issue of nested 'double quotes' and clears the unit tests. |
|
Date |
User |
Action |
Args |
2010-04-12 21:48:46 | l0nwlf | set | recipients:
+ l0nwlf, barry, msapiro, rcoyner, r.david.murray |
2010-04-12 21:48:45 | l0nwlf | set | messageid: <1271108925.92.0.573095808926.issue5277@psf.upfronthosting.co.za> |
2010-04-12 21:48:44 | l0nwlf | link | issue5277 messages |
2010-04-12 21:48:44 | l0nwlf | create | |
|