Return-Path: Delivered-To: apmail-struts-user-archive@www.apache.org Received: (qmail 76162 invoked from network); 1 Nov 2006 20:47:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Nov 2006 20:47:08 -0000 Received: (qmail 53859 invoked by uid 500); 1 Nov 2006 20:47:09 -0000 Delivered-To: apmail-struts-user-archive@struts.apache.org Received: (qmail 53828 invoked by uid 500); 1 Nov 2006 20:47:09 -0000 Mailing-List: contact user-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list user@struts.apache.org Received: (qmail 53817 invoked by uid 99); 1 Nov 2006 20:47:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2006 12:47:09 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of donald.brown@gmail.com designates 64.233.166.180 as permitted sender) Received: from [64.233.166.180] (HELO py-out-1112.google.com) (64.233.166.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Nov 2006 12:46:56 -0800 Received: by py-out-1112.google.com with SMTP id a25so232596pyi for ; Wed, 01 Nov 2006 12:46:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FvPd0ZmUGQXDkXbstnfwSC6XD9OeLJaC/LBUDuxRbLNj9g4o9MNuLdksWvEyLhB1WNGmnHsBenrinvtgOjbok81Dpy1MlilWu5Fpy3R+nPrk4rBaExjI5am3lZY+h9igFPikKImGvWKbiEsgSqBSTou6tae9SfAt1+WnT8P7xdM= Received: by 10.35.132.20 with SMTP id j20mr9599582pyn; Wed, 01 Nov 2006 12:46:35 -0800 (PST) Received: by 10.35.52.7 with HTTP; Wed, 1 Nov 2006 12:46:35 -0800 (PST) Message-ID: <1c661f2f0611011246y6cc6beb9sa736fda9e1463271@mail.gmail.com> Date: Wed, 1 Nov 2006 12:46:35 -0800 From: "Don Brown" To: "Struts Users Mailing List" Subject: Re: SSL support [s2] In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org There currently isn't anything like this in Struts 2, however, it would be easy to implement as an Interceptor. The SSL extension for Struts 1 also does some other interesting things that should also be considered like a secure link tag and redirect support with the same context. I'd start by porting the RequestProcessor code to an Interceptor, and perhaps have it key off a @Secure annotation on the action method instead. The SSL port would be a parameter of the interceptor. Then, you could include the interceptor in your default stack. As for the link tag, simply override the template for the link tag and have it generate a different url. You might need to create a new tag, actually. If you create the interceptor, please consider donating it to Struts 2, as that'd be a great feature to support out of the box. Don On 11/1/06, Jim Reynolds wrote: > Considering upgrading a site from Struts 1.x to Struts 2. Looking back > through the code there was a SSL Extension I used that allowed me to > set a true/false in the action as to whether or not the action was > going to be SSL or normal. > > This all extended from the RequestProcessor, so with S2, I am trying > to figure out how this is to be done. > > Sincerely > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org > For additional commands, e-mail: user-help@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@struts.apache.org For additional commands, e-mail: user-help@struts.apache.org