I have a web app that was developed many years ago to serve PDF "templates" with user data inserted into it's forms via FDF. Up until Adobe Reader 10.1.1 (currently testing with this version, possibly affects earlier versions of 10 too...), it stopped working in many browsers. I just tried with Reader v9.4.0 and it works fine as expected.
Here's a sample of some test from the app:
1 0 obj <<
<</Root 1 0 R>>
Did the FDF syntax change in 10.1? Can someone help me out please?
Did you check your security settings & trusted locations to ensure that the URL is on a trusted site??
Reply-To: "firstname.lastname@example.org<mailto:email@example.com>" <firstname.lastname@example.org<mailto:email@example.com>>
Date: Tue, 18 Oct 2011 13:36:13 -0700
Subject: Re: FDF no longer works in Reader 10.1.1. Worked in 9.x and previous FDF no longer works in Reader 10.1.1. Worked in 9.x and previous
FDF no longer works in Reader 10.1.1. Worked in 9.x and previous
Good advice. I've checked the security settings, they're set like this (v10.1.1 in a clean WinXP VirtualPC):
- Enable Enhanced Security (checked)
- Added host to privileged locations ('mysite.com')
IE6: doesn't work: opens new window and doesn't load anything, grey background (sadly the client requires this to work the most)
FF7: works fine
O11: doesn't work: Adobe Reader error - "File does not begin with '%PDF-'.
Chrome14: doesn't work: opens new tab and downloads serve_pdf.cfm which has only the FDF data in it
Tried in IE9 in Win7 on different PC: works fine
I would say that overall it's still not working. Any one else have any ideas?
Actually, I would say that overall it's working: It works with FF and a
current version of IE. IE6 is not supported by Acrobat X so I would not
expect it to work. Opera and Chrome are also not listed as supported
browsers by Acrobat X, so again, I would not expect those to work. You can
check the specs for Acrobat X here:
Karl Heinz Kremer
PDF Acrobatics Without a Net
I'm having the exact same probelm as daniel11223344. It's not working in IE8, and since XP and IE8 are still supported by microsoft, then I would say that this is a problem that should be fixed, or should have some sort of work-around for it. I can confirm this problem is still present in Reader 10.0.3
Any help woudl be GREATLY appreciated!!