On Wed, September 27, 2006 9:00 am, Sam Smith wrote: > When loaded into a browser that can display PDF files (Win IE and > Firefox, Mac Safari) the FDF file (snip below) should open linked PDF > and populated it with the data from the FDF file. > > It works fine when the FDF file is loaded from within the browser > with "Open File" (or simply double-clicked from the desktop). > > It works fine in Win IE (because IE doesn't play by the rules). > > I just don't understand the header thing, the "Content-type" deal. > > Why is the FDF file loaded as plain text when loaded via a URL? > > <http://arraymedia.com/csz/pdf/ud/JO_SAFARI_FORM_AND_DATA/> Standards-based browsers (everything but IE) wants the Content-type so they know what the [bleep] kind of document you are handing them. IE examines the URL, the contents of the document, the META tags (in HTML) the range of values of the bytes in the document (to guess at charset) -- Pretty much, IE does everything it possibly can to NOT follow the standard Content-type. They must have an entire team of engineers maintaining the "guess what type this might be" code-base. So in your case, the lack of .pdf and .fdf on the end are killing you in IE. If it don't work in the others, the lack of an appropriate Content-type is killing you. Here is an article specifically about FDF|PDF: http://phpbootcamp.com/articles/fdf.htm NOTE: You also can *NOT* have GET arguments for FDF->PDF if you have configured the Adobe Reader to open in its own window on IE. The GET args will confuse IE and make it not launch the Reader. In some versions of IE, at least. Also read the second half of this article: http://richardlynch.blogspot.com/ It's really all about the same thing -- Don't confuse the browsers with dynamic rich media. Make them *think* they are getting static rich media. (rich media: images, PDFs, SWF, etc) -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
