Forum Discussion
IE/Chrome unable to open PDF version 1.6 file via F5 LTM with SSL terminated on the F5
We have an internal site with SSL terminated on the F5. Users are unable to open pdf version 1.6 files through the F5 SSL. Version 1.4 and 1.5 files open just fine. If we hit the web servers direct (non-ssl), the 1.6 file opens just fine.
I've seen several articles about PDF's not opening doing to cache'ing, etc. I've tried adding an irule to match on content-type "application/pd" to then set the http response header pragma and cache-control to public...also tried removing those headers. Neither seems to have helped. Has anyone else ever run into this issue?
The error we see in IE is "The file is damaged and could not be repaired. Local\EWH&yy".
Thanks!
1 Reply
- Brad_Parker
Cirrus
This could possibly be a chunking or compression issue. The only real way to find the problem would be a deep dive packet analysis. But, just for a shot in the dark try editing you HTTP profile and change response chunking to preserve. Another diagnostic attempt you could also ensure your web server isn't compressing the pdf(this will slow down transfer speed).
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
