I am baffled by bizarre servlet behavior using IE4.0 and IE5.0
browsers to do a GET. The behavior does not happen under Netscape
Communicator 4.51. Any help on where to even begin looking would be
greatly appreciated!

Configuration:
    WinNT 4.0, SVP4
    MSVC5.0
    Apache 1.3.6
    ApacheJServ 1.0b4   (Given that I could not find an apachecore.lib
                         and ApacheModuleJServ.dll, it was painful to 
                         install 1.0b4, and I had to build from the 
                         latest versions of the files rather 
                         than those that came in Apache-JServ-1.0b4.tar.gz.
                         I wonder how others have done the same?)

Upon receiving a GET, my servlet can either send back "text/html"
content or "application/pdf" content, depending on the input
parameters.  

With Netscape Communicator 4.51, the right thing happens, i.e.,
when I send back the PDF, the Acrobat Viewer is fired up within
Netscape and the file is displayed.

My problem comes under IE4.0 and IE5.0 when sending back
PDFs. Here are the facts:

* Sending back "text/html" works fine.

* Under an earlier version of Apache (1.3.4) and ApacheJServ (1.0b3),
Acrobat Exchange would be launched, but Acrobat would hang with
the Task Manager showing Acrobat "not responding" and showing 100% CPU
usage until the Acrobat application was killed. As before, "text/html"
worked fine.

* Under Apache 1.3.6/ApacheJServ 1.0b4, for each submit, i.e., GET,
there are THREE, count'em THREE, executions of my servlet, and three
GETs showing up in access.log! The output file is then shown.
(Actually,I am not sure which of the three output files is actually
being served to Acrobat.)

* As I said before, under Netscape Communicator 4.51, the servlet 
runs as expected, with one GET showing up in access.log and my
servlet running only once.

Ideas?????

Thanks very much,
Jeff Finger



------------------------------------------------------------
To subscribe:    [EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Problems?:       [EMAIL PROTECTED]

Reply via email to