Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Mime-Version: 1.0 (Apple Message framework v609)
In-Reply-To: <200312221101.22871.thad@mindwrap.com>
References: <200312181510.23157.thad@mindwrap.com>
 <57F892EC-336E-11D8-B236-00306557E112@u.washington.edu>
 <200312221101.22871.thad@mindwrap.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C05DA3FA-3D35-11D8-A743-00306557E112@u.washington.edu>
Content-Transfer-Encoding: 7bit
From: Michael Becke <becke@u.washington.edu>
Subject: Re: Passing HttpClient Header back to the browser
Date: Fri, 2 Jan 2004 10:10:07 -0500
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>

Hi Thad,

The problem has nothing to do with Struts or HttpClient I believe.  It 
is because a cookie is required to access the site.  Since there is no 
way to set cookies on the browser from an applet, the cookie must be 
set by the web server when the browser authenticates.  You would have 
the same problem when using the java URLConnection and some other web 
application framework.

Mike

On Dec 22, 2003, at 11:01 AM, Thad Humphries wrote:

> Yes, that is how it will probably work in the final product but I'm in 
> a
> evaluation phase now.  Key to this evaluation is getting applets and 
> struts
> to work together and the login applet is an easy one to test with.  We 
> have
> other applets that are far more complex and far more critical to the
> application.  These applets *must* be able to seemlessly return 
> control to
> the browser.  For example, there are database index and query screens 
> (often
> complex) created and viewed on fat clients that we can also render in 
> Swing
> applets.  There's no problem opening these applets but if they can't 
> return
> control to the browser we're left to render the hitlist in an applet 
> which is
> an non-starter.  We also have a TIFF image viewer applet that must 
> interact
> with the server or image and annotation data.
>
> This stuff works without Struts and HTTPClient.  I would, however, 
> like to
> rework it for Struts because I think Struts will be more flexible as 
> the
> application grows.
>
> On Saturday 20 December 2003 23:30, Michael Becke wrote:
>> ...
>> Even if you can get things working using this system I would suggest
>> something different. In particular I suggest handling the
>> authentication within the browser and then passing the cookie to the
>> applet.  You can pass the cookie to the applets via a parameter in the
>> applet HTML.  The JSPs have access to the session ID of the request 
>> and
>> can write it into the applet page.
>> ...
>
> -- 
> Thad Humphries                 "...no religious test shall ever be 
> required
> Web Development Manager         as a qualification to any office or 
> public
> Phone: 540/675-3015, x225       trust under the United States." 
> -Article VI
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org