Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-18 Thread Aman Raheja
Some more info to respond to the earlier responses
1) We're seeing more evidence this is a problem with Reader 6.0.1 (or 
the 6.0.2 patch).  We have a PC with Reader 6.0.0 that works Ok, as well 
as a PC with 5.0.  Our company has done a mass upgrade to Reader 6.0.1 
and IE 6.0.2, so these PCs are not the norm.
2) No SSL is being used at this point (but it will eventually).
3) No compression (that I know of -- unless Tomcat is doing it for us).
4) Our JSP is supposed to be a generic file downloader, handling Word, 
Excel, PDF, etc.   Hence the URL ends in .jsp vs. the real file 
extension.
5) Here's a typical response we're getting in IE:

HTTP/1.0 200 OK
Date: Wed, 17 Nov 2004 20:33:26 GMT
Server: Apache Tomcat/4.0.6 (HTTP/1.1 Connector)
Content-Type: application/pdf;charset=ISO-8859-1
Content-Length: 156483
Content-disposition: attachement; filename=Germany.pdf
expires: Thu, 01 Jan 1970 00:00:00 GMT
Connection: close
Thanks,
Aman Raheja

Phillip Qin wrote:
Where do you generate the pdf? In servlet? The link has to be end with .pdf
(but before any query string) in order for acrobat reader active-x to kick
in.
-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in

We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja
Phillip Qin wrote:
 

There are security and privacy settings in IE affect PDF generation. 
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX Reader
Plug-in
Problem:
When we try to display a dynamically generated PDF file, IE launches 
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:
- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800
Additional Information:
1) Our URLs are formed like this:
http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research
2) Our app is issuing GETs, not POSTs.
3) This is happening on multiple PCs.  One thing we noticed is this may
be somewhat Reader version dependent -- we have a few machines left with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the
document that didn't display in the IE window is automatically displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2
that works.  Could this problem be caused by some specific Windows or IE 
patch?

7) We've scoured the forums and tried several things including setting
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6
adding charset=ISO-8859-1 to the Content-Type header in the response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!DSPAM:419a0e4b161771045017228!
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-18 Thread David Wall
Have you tried using links like the following:

http://yourhost.com/webappcontext/download.jsp/Germany.pdf

The idea is that tomcat will find the JSP download.jsp and execute it, and
since the link ends with the file name, some browsers will better detect the
pdf reader launch.

If you need some params passed in, your link would look like:

http://yourhost.com/webappcontext/download.jsp/Germany.pdf?abc=xyzxyz=abc

I don't know if your headers have a typo in your email or in production, but
you have an invalid Content-Disposition header (misspelled attachment as
attachement) which would be a problem, too.

David

- Original Message - 
From: Aman Raheja [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 8:47 AM
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


 Some more info to respond to the earlier responses

 1) We're seeing more evidence this is a problem with Reader 6.0.1 (or
 the 6.0.2 patch).  We have a PC with Reader 6.0.0 that works Ok, as well
 as a PC with 5.0.  Our company has done a mass upgrade to Reader 6.0.1
 and IE 6.0.2, so these PCs are not the norm.
 2) No SSL is being used at this point (but it will eventually).
 3) No compression (that I know of -- unless Tomcat is doing it for us).
 4) Our JSP is supposed to be a generic file downloader, handling Word,
 Excel, PDF, etc.   Hence the URL ends in .jsp vs. the real file
 extension.
 5) Here's a typical response we're getting in IE:

 HTTP/1.0 200 OK
 Date: Wed, 17 Nov 2004 20:33:26 GMT
 Server: Apache Tomcat/4.0.6 (HTTP/1.1 Connector)
 Content-Type: application/pdf;charset=ISO-8859-1
 Content-Length: 156483
 Content-disposition: attachement; filename=Germany.pdf
 expires: Thu, 01 Jan 1970 00:00:00 GMT
 Connection: close


 Thanks,
 Aman Raheja



 Phillip Qin wrote:

 Where do you generate the pdf? In servlet? The link has to be end with
.pdf
 (but before any query string) in order for acrobat reader active-x to
kick
 in.
 
 -Original Message-
 From: Aman Raheja [mailto:[EMAIL PROTECTED]
 Sent: November 16, 2004 9:27 AM
 To: Tomcat Users List
 Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX
R
 eader Plug-in
 
 
 We did set the Security level to low on IE.
 More suggestions?
 Thanks
 Aman Raheja
 
 Phillip Qin wrote:
 
 
 
 There are security and privacy settings in IE affect PDF generation.
 BTW, ensurethe link before query string ends with .pdf
 
 -Original Message-
 From: Aman Raheja [mailto:[EMAIL PROTECTED]
 Sent: November 15, 2004 1:40 PM
 To: [EMAIL PROTECTED]
 Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX
Reader
 Plug-in
 
 
 Problem:
 
 When we try to display a dynamically generated PDF file, IE launches
 the
 Adobe Acrobat Reader Plugin, but then just a blank page is displayed and
 the IE status says Done.  No error message is displayed.  No error is
 generated in the System Event logs.
 
 The issue seems to be that every request to request to Tomcat for the
 PDF send back the request with charset=ISO-8859-1 in the
 Content-type Header. We want to figure out a way to verify that this
 is the issue. One way might be to somehow get Tomcat to not append the
 Character Set in the header. Is there a way to do this?
 
 Environment:
 
 - Client: Windows XP or Windows 2000
 - Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
 (problem exists on both)
 - Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
 - IE 6.0.2800
 
 
 Additional Information:
 
 1) Our URLs are formed like this:
 
 http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
 Name=
 Germanyentry=DocType=pdfcategory=Research
 
 2) Our app is issuing GETs, not POSTs.
 
 3) This is happening on multiple PCs.  One thing we noticed is this may
 be somewhat Reader version dependent -- we have a few machines left with
 Reader 5 installed, and they do not seem to have the problem.
 
 4) When the problem occurs, if you then launch Reader manually, the
 document that didn't display in the IE window is automatically displayed
 in the full client Reader app.!!!
 
 5) If we set Reader to not open up PDFs in browser windows, the Reader
 window launches and opens the PDF file just fine.   [This is a client
 solution, and not practical to implement across hundreds of PCs
 unfortunately.]
 
 6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2
 that works.  Could this problem be caused by some specific Windows or IE
 patch?
 
 7) We've scoured the forums and tried several things including setting
 all security levels to Low in IE, adding a dummy parm at the end of the
 URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf),
 and various header settings to force caching on to 30 seconds, etc.
 None of this had any effect.
 
 8) Also, we saw some references to problems caused by Tomcat 4.0.6
 adding charset=ISO-8859-1 to the Content-Type header in the response.
 How can we

Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-18 Thread Aman Raheja
Here's some more input from our team, regarding the problem
We've confirmed its defintely the charset=ISO-8859-1 appended to the 
Content-Type header that is causing the problem in IE.  [I'm not saying 
IE shouldn't work with this, but we don't have a choice but to support 
it.]  We wrote a stand-alone servlet that works fine downloading a 
pdf if we leave off the charset.  When we add the charset to the header, 
it breaks.  It looks like when Tomcat is compiling our JSP code, its 
adding the charset into the response based on what we see in the 
intermediate Java code the Jasper compiler is producing.

--- Does anyone know how to override this on Tomcat 4.0.6 specifically?
FYI:  We read that this was a known issue in another forum, and some 
version of Tomcat 4.1 might be changed to leave this off.  However, we 
experimented with Tomcat 4.0.6/JDK 1.3.1, Tomcat 4.1.31/JDK 1.4.2, and 
Tomcat 5.5.4/JDK 1.5.0, and all these combinations add the charset to 
the response.

Meantime we are checking on the mis-spelled attachment for 
Content-Disposition part of the header dump we sent earlier.


David Wall wrote:
Have you tried using links like the following:
http://yourhost.com/webappcontext/download.jsp/Germany.pdf
The idea is that tomcat will find the JSP download.jsp and execute it, and
since the link ends with the file name, some browsers will better detect the
pdf reader launch.
If you need some params passed in, your link would look like:
http://yourhost.com/webappcontext/download.jsp/Germany.pdf?abc=xyzxyz=abc
I don't know if your headers have a typo in your email or in production, but
you have an invalid Content-Disposition header (misspelled attachment as
attachement) which would be a problem, too.
David
- Original Message - 
From: Aman Raheja [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 8:47 AM
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in

 

Some more info to respond to the earlier responses
1) We're seeing more evidence this is a problem with Reader 6.0.1 (or
the 6.0.2 patch).  We have a PC with Reader 6.0.0 that works Ok, as well
as a PC with 5.0.  Our company has done a mass upgrade to Reader 6.0.1
and IE 6.0.2, so these PCs are not the norm.
2) No SSL is being used at this point (but it will eventually).
3) No compression (that I know of -- unless Tomcat is doing it for us).
4) Our JSP is supposed to be a generic file downloader, handling Word,
Excel, PDF, etc.   Hence the URL ends in .jsp vs. the real file
extension.
5) Here's a typical response we're getting in IE:
HTTP/1.0 200 OK
Date: Wed, 17 Nov 2004 20:33:26 GMT
Server: Apache Tomcat/4.0.6 (HTTP/1.1 Connector)
Content-Type: application/pdf;charset=ISO-8859-1
Content-Length: 156483
Content-disposition: attachement; filename=Germany.pdf
expires: Thu, 01 Jan 1970 00:00:00 GMT
Connection: close
Thanks,
Aman Raheja

Phillip Qin wrote:
   

Where do you generate the pdf? In servlet? The link has to be end with
 

.pdf
 

(but before any query string) in order for acrobat reader active-x to
 

kick
 

in.
-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX
 

R
 

eader Plug-in
We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja
Phillip Qin wrote:

 

There are security and privacy settings in IE affect PDF generation.
BTW, ensurethe link before query string ends with .pdf
-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX
   

Reader
 

Plug-in
Problem:
When we try to display a dynamically generated PDF file, IE launches
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and
the IE status says Done.  No error message is displayed.  No error is
generated in the System Event logs.
The issue seems to be that every request to request to Tomcat for the
PDF send back the request with charset=ISO-8859-1 in the
Content-type Header. We want to figure out a way to verify that this
is the issue. One way might be to somehow get Tomcat to not append the
Character Set in the header. Is there a way to do this?
Environment:
- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800
Additional Information:
1) Our URLs are formed like this:
http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research
2) Our app is issuing GETs, not POSTs.
3) This is happening on multiple PCs.  One thing we noticed is this may
be somewhat Reader version dependent -- we have a few machines left with
Reader 5 installed, and they do

RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-18 Thread Phillip Qin
If you can visit our site at
https://www.investments.shareowner.com/lciponline and view the sample pdf
statement, then there is something definitely wrong with your own code - do
not pointing to Tomcat.



-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 18, 2004 12:50 PM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


Here's some more input from our team, regarding the problem

We've confirmed its defintely the charset=ISO-8859-1 appended to the 
Content-Type header that is causing the problem in IE.  [I'm not saying 
IE shouldn't work with this, but we don't have a choice but to support 
it.]  We wrote a stand-alone servlet that works fine downloading a 
pdf if we leave off the charset.  When we add the charset to the header, 
it breaks.  It looks like when Tomcat is compiling our JSP code, its 
adding the charset into the response based on what we see in the 
intermediate Java code the Jasper compiler is producing.

--- Does anyone know how to override this on Tomcat 4.0.6 specifically?

FYI:  We read that this was a known issue in another forum, and some 
version of Tomcat 4.1 might be changed to leave this off.  However, we 
experimented with Tomcat 4.0.6/JDK 1.3.1, Tomcat 4.1.31/JDK 1.4.2, and 
Tomcat 5.5.4/JDK 1.5.0, and all these combinations add the charset to 
the response.


Meantime we are checking on the mis-spelled attachment for 
Content-Disposition part of the header dump we sent earlier.




David Wall wrote:

Have you tried using links like the following:

http://yourhost.com/webappcontext/download.jsp/Germany.pdf

The idea is that tomcat will find the JSP download.jsp and execute it, 
and since the link ends with the file name, some browsers will better 
detect the pdf reader launch.

If you need some params passed in, your link would look like:

http://yourhost.com/webappcontext/download.jsp/Germany.pdf?abc=xyzxyz=
abc

I don't know if your headers have a typo in your email or in 
production, but you have an invalid Content-Disposition header 
(misspelled attachment as
attachement) which would be a problem, too.

David

- Original Message -
From: Aman Raheja [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 8:47 AM
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


  

Some more info to respond to the earlier responses

1) We're seeing more evidence this is a problem with Reader 6.0.1 (or 
the 6.0.2 patch).  We have a PC with Reader 6.0.0 that works Ok, as 
well as a PC with 5.0.  Our company has done a mass upgrade to Reader 
6.0.1 and IE 6.0.2, so these PCs are not the norm.
2) No SSL is being used at this point (but it will eventually).
3) No compression (that I know of -- unless Tomcat is doing it for 
us).
4) Our JSP is supposed to be a generic file downloader, handling Word,
Excel, PDF, etc.   Hence the URL ends in .jsp vs. the real file
extension.
5) Here's a typical response we're getting in IE:

HTTP/1.0 200 OK
Date: Wed, 17 Nov 2004 20:33:26 GMT
Server: Apache Tomcat/4.0.6 (HTTP/1.1 Connector)
Content-Type: application/pdf;charset=ISO-8859-1
Content-Length: 156483
Content-disposition: attachement; filename=Germany.pdf
expires: Thu, 01 Jan 1970 00:00:00 GMT
Connection: close


Thanks,
Aman Raheja



Phillip Qin wrote:



Where do you generate the pdf? In servlet? The link has to be end 
with
  

.pdf
  

(but before any query string) in order for acrobat reader active-x to
  

kick
  

in.

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the 
ActiveX
  

R
  

eader Plug-in


We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja

Phillip Qin wrote:



  

There are security and privacy settings in IE affect PDF generation. 
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX


Reader
  

Plug-in


Problem:

When we try to display a dynamically generated PDF file, IE launches 
the Adobe Acrobat Reader Plugin, but then just a blank page is 
displayed and the IE status says Done.  No error message is 
displayed.  No error is generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for 
the PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that 
this is the issue. One way might be to somehow get Tomcat to not 
append the Character Set in the header. Is there a way to do this?

Environment:

- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP

Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread Aman Raheja
We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja
Phillip Qin wrote:
There are security and privacy settings in IE affect PDF generation. BTW,
ensurethe link before query string ends with .pdf
-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX Reader
Plug-in

Problem: 

When we try to display a dynamically generated PDF file, IE launches the 
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the 
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:
- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP 
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800

Additional Information:
1) Our URLs are formed like this: 

http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698DocName=
Germanyentry=DocType=pdfcategory=Research
2) Our app is issuing GETs, not POSTs.
3) This is happening on multiple PCs.  One thing we noticed is this may 
be somewhat Reader version dependent -- we have a few machines left with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the 
document that didn't display in the IE window is automatically displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs 
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2 
that works.  Could this problem be caused by some specific Windows or IE 
patch?

7) We've scoured the forums and tried several things including setting 
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6 
adding charset=ISO-8859-1 to the Content-Type header in the response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!DSPAM:4198f83938781679484274!
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread karjera

Laba diena.



Dkojame, kad mums parate.

Js atsista inut isaugota ms duomen bazje.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread David Boyer
Are you setting the MIME type in the response header properly for the
PDF? Also note that the Acrobat Reader plugin doesn't like to read PDFs
if they've been served using HTTP compression (I don't know if that
applies in your case or not).
 
Also, if the PDF is being sent over SSL, note that IE has a setting
that prevents the caching of SSL-delivered content to disk, which will
choke the Acrobat Reader plugin.

 [EMAIL PROTECTED] 11/16/2004 6:33:20 AM 

Where do you generate the pdf? In servlet? The link has to be end with
.pdf
(but before any query string) in order for acrobat reader active-x to
kick
in.

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the
ActiveX R
eader Plug-in


We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja

Phillip Qin wrote:

There are security and privacy settings in IE affect PDF generation. 
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX
Reader
Plug-in


Problem:

When we try to display a dynamically generated PDF file, IE launches 
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed
and 
the IE status says Done.  No error message is displayed.  No error
is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this

is the issue. One way might be to somehow get Tomcat to not append the

Character Set in the header. Is there a way to do this?

Environment:

- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800


Additional Information:

1) Our URLs are formed like this:

http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research

2) Our app is issuing GETs, not POSTs.

3) This is happening on multiple PCs.  One thing we noticed is this
may
be somewhat Reader version dependent -- we have a few machines left
with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the
document that didn't display in the IE window is automatically
displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader

window launches and opens the PDF file just fine.   [This is a client

solution, and not practical to implement across hundreds of PCs
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE
6.0.2
that works.  Could this problem be caused by some specific Windows or
IE 
patch?

7) We've scoured the forums and tried several things including
setting
all security levels to Low in IE, adding a dummy parm at the end of
the 
URL to fool IE into launching the PDF correctly (e.g.
dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6
adding charset=ISO-8859-1 to the Content-Type header in the
response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:419a0e4b161771045017228!



RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread Phillip Qin
Where do you generate the pdf? In servlet? The link has to be end with .pdf
(but before any query string) in order for acrobat reader active-x to kick
in.

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja

Phillip Qin wrote:

There are security and privacy settings in IE affect PDF generation. 
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX Reader
Plug-in


Problem:

When we try to display a dynamically generated PDF file, IE launches 
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:

- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800


Additional Information:

1) Our URLs are formed like this:

http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research

2) Our app is issuing GETs, not POSTs.

3) This is happening on multiple PCs.  One thing we noticed is this may
be somewhat Reader version dependent -- we have a few machines left with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the
document that didn't display in the IE window is automatically displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2
that works.  Could this problem be caused by some specific Windows or IE 
patch?

7) We've scoured the forums and tried several things including setting
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6
adding charset=ISO-8859-1 to the Content-Type header in the response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:419a0e4b161771045017228!


RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread Graff, David
I've developed a couple of applications that spit back PDF files from within
Struts.

One thing I did have to do was make sure the generated PDF's response
content type was application/pdf

I don't think I've had to do anything with filename extensions.

-Original Message-
From: Phillip Qin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 9:33 AM
To: 'Tomcat Users List'
Subject: RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX
R eader Plug-in


Where do you generate the pdf? In servlet? The link has to be end with .pdf
(but before any query string) in order for acrobat reader active-x to kick
in.

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja

Phillip Qin wrote:

There are security and privacy settings in IE affect PDF generation. 
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX Reader
Plug-in


Problem:

When we try to display a dynamically generated PDF file, IE launches 
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:

- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800


Additional Information:

1) Our URLs are formed like this:

http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research

2) Our app is issuing GETs, not POSTs.

3) This is happening on multiple PCs.  One thing we noticed is this may
be somewhat Reader version dependent -- we have a few machines left with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the
document that didn't display in the IE window is automatically displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2
that works.  Could this problem be caused by some specific Windows or IE 
patch?

7) We've scoured the forums and tried several things including setting
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6
adding charset=ISO-8859-1 to the Content-Type header in the response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:419a0e4b161771045017228!


RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread Phillip Qin
Mozilla does not have the extension issue. IE does. I use struts too.

-Original Message-
From: Graff, David [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:42 AM
To: 'Tomcat Users List'
Subject: RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


I've developed a couple of applications that spit back PDF files from within
Struts.

One thing I did have to do was make sure the generated PDF's response
content type was application/pdf

I don't think I've had to do anything with filename extensions.

-Original Message-
From: Phillip Qin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 9:33 AM
To: 'Tomcat Users List'
Subject: RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


Where do you generate the pdf? In servlet? The link has to be end with .pdf
(but before any query string) in order for acrobat reader active-x to kick
in.

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in


We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja

Phillip Qin wrote:

There are security and privacy settings in IE affect PDF generation.
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX 
Reader Plug-in


Problem:

When we try to display a dynamically generated PDF file, IE launches
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the 
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:

- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP 
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800


Additional Information:

1) Our URLs are formed like this:

http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research

2) Our app is issuing GETs, not POSTs.

3) This is happening on multiple PCs.  One thing we noticed is this may 
be somewhat Reader version dependent -- we have a few machines left 
with Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the 
document that didn't display in the IE window is automatically 
displayed in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs 
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2 
that works.  Could this problem be caused by some specific Windows or 
IE patch?

7) We've scoured the forums and tried several things including setting 
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6 
adding charset=ISO-8859-1 to the Content-Type header in the response.
How can we override this to see if that's the problem?

Thanks
Aman Raheja


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





!DSPAM:419a11f7162861134571087!


Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-16 Thread Aman Raheja
The pdf is at a relative path from the JSP that spawns the active-x.
The link would end with .pdf, but tomcat appends charset=ISO-8859-1 to 
the content header.
Thanks
Aman Raheja

Phillip Qin wrote:
Where do you generate the pdf? In servlet? The link has to be end with .pdf
(but before any query string) in order for acrobat reader active-x to kick
in.
-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 16, 2004 9:27 AM
To: Tomcat Users List
Subject: Re: Problem displaying PDF in IE6 from Tomcat using the ActiveX R
eader Plug-in

We did set the Security level to low on IE.
More suggestions?
Thanks
Aman Raheja
Phillip Qin wrote:
 

There are security and privacy settings in IE affect PDF generation. 
BTW, ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED]
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX Reader
Plug-in
Problem:
When we try to display a dynamically generated PDF file, IE launches 
the
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:
- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800
Additional Information:
1) Our URLs are formed like this:
http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698Doc
Name=
Germanyentry=DocType=pdfcategory=Research
2) Our app is issuing GETs, not POSTs.
3) This is happening on multiple PCs.  One thing we noticed is this may
be somewhat Reader version dependent -- we have a few machines left with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the
document that didn't display in the IE window is automatically displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2
that works.  Could this problem be caused by some specific Windows or IE 
patch?

7) We've scoured the forums and tried several things including setting
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6
adding charset=ISO-8859-1 to the Content-Type header in the response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!DSPAM:419a0e4b161771045017228!
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Problem displaying PDF in IE6 from Tomcat using the ActiveX R eader Plug-in

2004-11-15 Thread Phillip Qin
There are security and privacy settings in IE affect PDF generation. BTW,
ensurethe link before query string ends with .pdf

-Original Message-
From: Aman Raheja [mailto:[EMAIL PROTECTED] 
Sent: November 15, 2004 1:40 PM
To: [EMAIL PROTECTED]
Subject: Problem displaying PDF in IE6 from Tomcat using the ActiveX Reader
Plug-in


Problem: 

When we try to display a dynamically generated PDF file, IE launches the 
Adobe Acrobat Reader Plugin, but then just a blank page is displayed and 
the IE status says Done.  No error message is displayed.  No error is 
generated in the System Event logs.

The issue seems to be that every request to request to Tomcat for the 
PDF send back the request with charset=ISO-8859-1 in the 
Content-type Header. We want to figure out a way to verify that this 
is the issue. One way might be to somehow get Tomcat to not append the 
Character Set in the header. Is there a way to do this?

Environment:

- Client: Windows XP or Windows 2000
- Server: Tomcat 4.0.6/JDK 1.3.1 running on Solaris and Windows XP 
(problem exists on both)
- Adobe Reader 6.0.1 (occurs with 6.0.2 patch as well)
- IE 6.0.2800


Additional Information:

1) Our URLs are formed like this: 

http://app.ourserver.com/appname/docViewAGN.jsp?RepoType=CID=18698DocName=
Germanyentry=DocType=pdfcategory=Research

2) Our app is issuing GETs, not POSTs.

3) This is happening on multiple PCs.  One thing we noticed is this may 
be somewhat Reader version dependent -- we have a few machines left with 
Reader 5 installed, and they do not seem to have the problem.

4) When the problem occurs, if you then launch Reader manually, the 
document that didn't display in the IE window is automatically displayed 
in the full client Reader app.!!!

5) If we set Reader to not open up PDFs in browser windows, the Reader 
window launches and opens the PDF file just fine.   [This is a client 
solution, and not practical to implement across hundreds of PCs 
unfortunately.]

6) We actually have one PC with Windows XP, Reader 6.0.1, and IE 6.0.2 
that works.  Could this problem be caused by some specific Windows or IE 
patch?

7) We've scoured the forums and tried several things including setting 
all security levels to Low in IE, adding a dummy parm at the end of the 
URL to fool IE into launching the PDF correctly (e.g. dummy=file.pdf), 
and various header settings to force caching on to 30 seconds, etc.  
None of this had any effect.

8) Also, we saw some references to problems caused by Tomcat 4.0.6 
adding charset=ISO-8859-1 to the Content-Type header in the response.  
How can we override this to see if that's the problem?

Thanks
Aman Raheja


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:4198f83938781679484274!