Status: Unconfirmed
Owner: ----
Labels: Cr-Platform-Extensions Pri-2 Via-Wizard Type-Bug OS-Windows
New issue 477971 by
mgt...@gmail.com: Integrated PDF viewer doesnt work
when content-disposition header contains UMLAUTE
https://code.google.com/p/chromium/issues/detail?id=477971
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/42.0.2311.90 Safari/537.36
Steps to reproduce the problem:
1. Have Server return PDF File with Content-Disposition: inline;
filename="Test für us"
2. PDF is gray
What is the expected behavior?
Should display PDF
What went wrong?
German Umlaute are valid ISO-8859-1 characters. So I would have assumed
this to be ok with the Content-Disposition specs.
WebStore page: Chrome Internal PDF Viewer
Did this work before? N/A
Chrome version: 42.0.2311.90 Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 17.0 r0
attached node test program to reproduce.
As a side note: when the umlaut is uri encoded (%FC instead of ü) The file
is shown but the name is ignored, even though i would have assumed %FC to
be valid latin-1 characters as well (of course this would not decode into
an ü though)
Returning as UTF-8: e.g.
filename*=UTF-8''pdf%20mit%20name%20mit%20u%CC%88.pdf")
works but shouldnt be needed.
Attachments:
bug-chromium-pdf-content-disposition-encoding.zip 6.8 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings