of a cgi script I'd stuck in to test something. As it happened IE would show raw PDF while NE would show the image. Weird. As it happens, yes, the pdf exists, a previous cgi (don't ask) puts the link in only if the image/pdf file exists and I fully intended to move the mess to a perl script (for billing and other reasons) once I got the IE fiddle out of the way.echo "Content-Type: application/pdf\n\n" cat $path
The worser part is, the IE problem went away on its own, I can only think I was the victim of over caching. It was pointed out that IE ignores the content-type info and tries to figure out the incoming type on its own. While I had a version that worked in NE but not IE, my fixing must've been hampered by either BillG still mad about that node from so long ago or some cache problem, where the bad one kept reappearing. I am now using print PDF> (happily, I am using that exact filehandle name ;-), though I wonder if there is a need to use sysread instead of just open/print.
Actually, I wish either the CB had a scratch node area, or deleting a node were easier. But thanks for the advice.
a
In reply to Re: Re: Re: IE trouble
by a
in thread IE trouble
by a
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |