Looking at my generic PDF code (from 4 years ago it appears, wow...),
it looks like I'm doing almost exactly what George suggested, but my
content-type header is different:
response.setHeader( "application/pdf; name=\"" + fileName
() + "\"", "content-type" );
(Where fileName() is going to return a string with a .pdf extension.)
I don't recall running into your issue, so perhaps this will help
make sure apache doesn't think it knows better than you what the
content-type should be. ;-)
Regards,
Mark
On Mar 28, 2007, at 10:37 AM, Johann Werner wrote:
I found the cause of the problems to correctly display an inline
pdf. Apparently the header information "application/pdf" is
overwritten by Apache to "text/html". I suppose that it does so
because the URL doesn't end with ".pdf" but ends with the context ID.
How can I prevent Apache from ignoring the headers from WO or is it
possible to return a WOComponent (the PDF file) but with a
"corrected" URL?
Johann
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/markm%
40onpointsoftware.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
