Well, they are pretty significant. 3.3.x (at least until the yet-to-be-released 3.3.2) stand-alone ignores HTTP/1.1 headers on the request. Even 3.3.2 will ignore the "partial-request" that Adobe is so fond of issuing for a pdf (which is it's right under the HTTP/1.1 spec, even if it is not the recomended behavior).
At a guess, your servlet can't handle Adobe's "partial-request" statements, and is getting confused when Adobe issues multiple request for the same document. "Hugo Villeneuve" <[EMAIL PROTECTED]> wrote in message news:NFBBKMKLCMGJANFCBENAOEKLCEAA.hvilleneuve@;b-wax.com... > > Hello, > I was surprise how easy it was moving from tomcat 3.3 to 4.1. Except for > something, pdf files. I generate dynamically pdf file Inside a Struts > Action. > > I took me a while to figure out how to pop the Adobe reader inside MSIE 5 > browser by tweaking to response header (header key like Content-Disposition, > inline; filename=myFile.pdf ). Now avery think is working fine with IE5 and > tomcat 3.3 > When I switch to Tomcat 4 the browser does not pop the Adobe reader but ask > me to save the file on disk . I read some issues about calling a PDF via a > GET v.s a POST and I think the problem is there. > > What is the difference between Tomcat 3.2 HTTP Header and 4.1 Header ? > > Any information about that ? > > > My System : > - Win NT > - Struts 1.0 > - Tomcat 3.2 --- 4.1 > > thank you > > Hugo Villeneuve > www.b-wax.com > > > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
