Re: Request sent twice from IE5.5 and N6 when content type is app lication/pdf

[Lindsay, William (USPC.PCT.Hopewell)]

Hi Pierre-Yves,

        We put a workaround in to allow POST today. We chose to use a COOKIE to keep 
the Web Farm stateless. We set the COOKIE on every request, and retrieve the COOKIE 
only when NULLS arrive on the
Server. The COOKIE stores the unique document criteria, which we use to extract from 
the IBM's Content OnDemand. 

        This allows us to avoid any configuration of Adobe Acrobat from 3.x to 5.0.

        It also allows us to avoid the filesystem on the Webserver.

        Bill

-----Original Message-----
From: Pierre-Yves Saumont [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 19, 2001 10:54 AM
To: [EMAIL PROTECTED]
Subject: Re: Request sent twice from IE5.5 and N6 when content type is
app lication/pdf


Hi Bill,

Things are becoming clearer.
Obviously, this is an acrobat plugin issue. If there are parameters in a
POST request, the plugin sends a new request with no parameters. That's why
it doesn't work with POST. It could work with a POST request with no
parameters, but generally, POST is used with a HTML form containing a submit
button, which causes a parameter with the name and value of the button to be
sent.

For me, the workaround is clearly to use GET. It ends working fine with all
browsers with acrobat 4 plugin.

Pierre-Yves

-----Message d'origine-----
De : A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]De la part de
Lindsay, William (USPC.PCT.Hopewell)
Envoy� : jeudi 19 juillet 2001 14:35
� : [EMAIL PROTECTED]
Objet : Re: Request sent twice from IE5.5 and N6 when content type is
app lication/pdf


I'm dealing with the same issue. What I've found so far is, when using GET
the URL+ARGS, let say
http://myurl/mypath/myservletalias.pdf?arg1=aaaa&arg2=bbbb

ELiminates the subsequent requests on the Servlet. I also moves the problem
to the Client, because ADOBE looks at the URL String, if it sees XYZ.PDF
(nothing more) it passes the content without
various client configurations in the Reader/Browser(s). This works back to
ADOBE 3x in our tests.

I've seen a workaround by caching the Original Request Parameters in
SESSION...???? and when NULL arrives, retrieve the PARAMS and reexec the
REQUEST. This only works for UNBALANCED web servers (we
are load balancing) so I'm still in need of a FIX.

Anybody else ????

Bill

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html