https://bz.apache.org/bugzilla/show_bug.cgi?id=66512
--- Comment #11 from Mark Thomas <ma...@apache.org> --- Alex, You might want to test an updated header as if you look at the "working" one: content-disposition: inline; filename="5_???? EL.pdf"; filename*=UTF-8''5_%CE%A0%CE%A1%CE%9F%CE%A3%20EL.pdf the filename is corrupted (the ???? characters). Fixing the header is (in my view) the best/correct long term option. The next Tomcat release round (April) will contain a fix that aligns AJP behaviour with HTTP behaviour (at least I am intending to include such a fix and will link it to this bug when I do). Given you said that mod_proxy_http worked, that should address this issue. I would caution you to test that before relying on it as my expectation is that it will cause the content-disposition header to be dropped. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
