I have found the problem.
It was a IE issues with the Cache-Control header parameter. Under HTTP 1.0
(Tomcat 3.3) IE5 and Adobe gets pdf correctly. With HTTP 1.1 and the use of
Cache-Control=no-cache IE5  keep asking to save the PDF file.. MS is suppose
to send SP4 in november.

Thank you all.


PS: there is ten time more action/response in this apache mailing list then
any Oracle Forums (when forum is working).


-----Original Message-----
From: Hugo Villeneuve [mailto:hvilleneuve@;b-wax.com]
Sent: Friday, November 15, 2002 11:57 AM
To: Tomcat Users List
Subject: RE: Serving PDF files gets different results from Tomcat 3.3 to
4.1


I don not touch the PDF. I get a valid PDF out of a DataBase as a blob.

-----Original Message-----
From: Nicholas Pappas [mailto:pappas@;cs.nyu.edu]
Sent: Friday, November 15, 2002 12:03 PM
To: Tomcat Users List
Subject: Re: Serving PDF files gets different results from Tomcat 3.3 to
4.1


What exactly are you using to generate the pdf-- home-grown code or Adobe
Distiller?  If your own code, are you sure you're creating the file itself
properly?

Hugo Villeneuve wrote:

> I am all confused now. All the test I did make it looks like a Adobe
problem
> but :
>
> 1-      When I call static PDF from tomcat 4.1 : PDF open in the IE5 (ok)
> 2-      When I call a pdf from my servlet  in tomcat 4.1 : IE5 ask to save
file
> (bad).
> 3-      When I right click on the URL and ask for "open in new Window"  :
PDF
> open in IE5 (ok) !!!.
> 4-      All condition above works on tomcat 3.3 !!
>
> Base on the header dump I did with telnet (thanks to Tim) (see below) It
> looks like Adobe threat HTTP 1.1 (tomcat 4.1) and HTTP 1.0 (tomcat 3.3) in
a
> different manner. I read some issues about calling PDf via GET or POST...
>
> If you have any Idea what could cause the problem base from the header
below
> please let me know. Un less I will keep looking on Adobe and IE news
group.
>
> //--------- Call a Static PDF, Tomcat 4.1 (open ok on IE5)-----
> GET /ocian/bug-mime.pdf HTTP/1.1
> connection: close
> host: hugo
>
> HTTP/1.1 200 OK
> ETag: W/"22649-1037304708111"
> Last-Modified: Thu, 14 Nov 2002 20:11:48 GMT
> Content-Length: 22649
> Date: Fri, 15 Nov 2002 15:27:34 GMT
> Server: Apache Coyote/1.0
> Connection: close
>
> //--------- Call to Dynamic PDF, Tomcat 4.1 (IE 5ask for save, bad)-----
> GET /ocian/renderer/renderPdfForm.do HTTP/1.1
> connection: close
> host:hugo
>
> HTTP/1.1 200 OK
> Set-Cookie: JSESSIONID=380EC9BAF52E335EBCA0759930ACC311; Path=/ocian
> Content-Type: application/pdf
> Pragma: no-cache
> Cache-Control: no-cache
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 22649
> Content-Disposition: inline; filename=myDoc.pdf
> Date: Fri, 15 Nov 2002 15:58:01 GMT
> Server: Apache Coyote/1.0
> Connection: close
>
> ------------ Call to Dynamic PDF Tomcat 3.3 (open ok on IE5)-------------
> HTTP/1.0 200 OK
> Content-Type: application/pdf
> Pragma: no-cache
> Cache-Control: no-cache
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 1361957
> Content-Disposition: inline; filename=OcianForm_102040.pdf
> Set-Cookie: JSESSIONID=8amd9yad71;Path=/ocian
> Date: Fri, 15 Nov 2002 16:06:15 GMT
> Server: Tomcat Web Server/3.3.1 Final ( JSP 1.1; Servlet 2.2 )
>
> ------------ Ops, did not know Tomcat 3.3 does not support HTTP
> 1.1 -------------
> GET /ocian/renderer/renderPdfForm.do?path=/:102040 HTTP/1.1
> connection:close
> host:xian
>
> HTTP/1.0 501 Not Implemented
> Content-Type: text/html
> Content-Length: 224
> Date: Fri, 15 Nov 2002 16:01:50 GMT
> Server: Tomcat Web Server/3.3.1 Final ( JSP 1.1; Servlet 2.2 )
> Thank you all.
>
> -----Original Message-----
> From: Tim Funk [mailto:funkman@;joedog.org]
> Sent: Friday, November 15, 2002 10:21 AM
> To: Tomcat Users List
> Subject: Re: Serving PDF files gets different results from Tomcat 3.3 to
> 4.1
>
> Examine the HTTP headers coming back. It may be as easy as
> adding/removing a new header.
>
> How to look at headers coming back:
> telnet webserver.running.tomcat3 80
> GET /myServet/givesme/pdfFile HTTP/1.1
> Connection: Close
> Host: needsFilledIn
>
> Then repeat for your tomcat 4 version.
>
> -Tim
>
> Ralph Einfeldt wrote:
> > Some options: (All not very nice)
> > - run tomcat behind apache.
> > - rewrite your servlet to implement http1.1
> >   (Have a look at the tomcat source of the tomcat
> >    servlet that serves the files (Can't remember
> >    the name)
> > - store the blob in the file system and redirect
> >   the browser to that file (so tomcat would serve
> >   the file)
> > - Don't know if there is a possibility to downgrade
> >   the http version in tomcat.
> >
> >
> >>-----Original Message-----
> >>From: Hugo Villeneuve [mailto:hvilleneuve@;b-wax.com]
> >>Sent: Friday, November 15, 2002 3:39 PM
> >>To: Tomcat Users List
> >>Subject: RE: Serving PDF files gets different results from
> >>Tomcat 3.3 to
> >>4.1
> >>
> >>I don't know much about "partial-request" and the HTTP 1.1
> >>Header (I will read about that) but for now all my tests
> >>make it looks like a combination of Adobe with Tomcat 4.1 problem.
> >>
> >>What do you suggest?
> >>Dropping Tomcat 4.1 and go back on tomcat 3.3 to fix header
> >>issues ( I can
> >>not drop Adobe...) ?
> >>Can I use the Servlet API to fix my problem ?
> >>
> >
> >
>
> --
> To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:tomcat-user-help@;jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
<mailto:tomcat-user-help@;jakarta.apache.org>

--
Nicholas Pappas



--
To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@;jakarta.apache.org>


--
To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@;jakarta.apache.org>



--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Reply via email to