Filename attachments sent with headers like below are getting corrupted
name in rt (4.0.6 here).
For example instead of “rozmowy wstępne - rozliczenie za kwiecień.xlsx”
rt displays truncated name “Download rozmowy wstępne -;
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet 6.2k”
Any chances to get this fixed?
Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet;
name=“rozmowy =?UTF-8?B?d3N0xJlwbmUgLSByb3psaWN6ZW5pZSB6YSBrd2llY2llxYQueGxzeA==?=”
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename0=UTF-8’'%72%6F%7A%6D%6F%77%79%20%77%73%74%C4%99%70%6E%65%20%2D;
filename1=%20%72%6F%7A%6C%69%63%7A%65%6E%69%65%20%7A%61%20%6B%77%69%65;
filename2=%63%69%65%C5%84%2E%78%6C%73%78
Arkadiusz Miśkiewicz, arekm / maven.pl
Hi,
Should work in 4.0.6.On Tue, Jun 26, 2012 at 1:25 PM, Arkadiusz Miśkiewicz arekm@maven.pl wrote:
Filename attachments sent with headers like below are getting corrupted
name in rt (4.0.6 here).
For example instead of “rozmowy wstępne - rozliczenie za kwiecień.xlsx”
rt displays truncated name “Download rozmowy wstępne -;
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet 6.2k”
Any chances to get this fixed?
Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet;
name=“rozmowy =?UTF-8?B?d3N0xJlwbmUgLSByb3psaWN6ZW5pZSB6YSBrd2llY2llxYQueGxzeA==?=”
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename0=UTF-8’'%72%6F%7A%6D%6F%77%79%20%77%73%74%C4%99%70%6E%65%20%2D;
filename1=%20%72%6F%7A%6C%69%63%7A%65%6E%69%65%20%7A%61%20%6B%77%69%65;
filename2=%63%69%65%C5%84%2E%78%6C%73%78
–
Arkadiusz Miśkiewicz, arekm / maven.pl
Best regards, Ruslan.
Hi,
Should work in 4.0.6.
Ohh, seems to be working for new emails. Thanks!
Arkadiusz Miśkiewicz, arekm / maven.pl
Hi,
Should work in 4.0.6.
But for me it don’t work in 3.8.13.
I send an message to the devel list on 2012-06-22 but didn’t any reply
until now.
Chris
Am 27.06.2012 22:53, schrieb Ruslan Zakirov:
Hi,
Should work in 4.0.6.
But for me it don’t work in 3.8.13.
I send an message to the devel list on 2012-06-22 but didn’t any reply
until now.
We can not backport every fix to 3.8 series. It’s not a regression as it didn’t
work in 4.0.0. You can backport 06b0d1273c3b87a979fc10cbdd0d5ad8edfadd00
to 3.8 and send patch back.
Chris
Best regards, Ruslan.