Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
MIME-Version: 1.0
In-Reply-To: 
 <CANrzj0k9hquJP+zfe1VBVAXnPHr=eTuRN+A7kDjv6ntr_4XhGA@mail.gmail.com>
References: 
 <CAPFNckhAhkoaMXmKufAY=tz64BROayrftDyZ-xVT6ESRddQ6EQ@mail.gmail.com>
 <CAHB4ARtvAkRfGDmFuRk1jwqrQgUW3Lp5b_DgHU6tb6ofMQyQ_g@mail.gmail.com>
 <CANrzj0k9hquJP+zfe1VBVAXnPHr=eTuRN+A7kDjv6ntr_4XhGA@mail.gmail.com>
From: Lukasz Lenart <lukaszlenart@apache.org>
Date: Thu, 16 May 2013 21:48:14 +0200
Message-ID: 
 <CAMopvkOsgPZXGxw+4BvYFU42NXymLw1HLn8XF4-MBTfZLAOoaw@mail.gmail.com>
Subject: Re: Cookie Interceptor
To: Struts Developers List <dev@struts.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

If this is gonna break backward compatibility, please register an
issue with JIRA and we will introduce the change with Struts 2.5/3
version.


Regards
--=20
=C5=81ukasz
+ 48 606 323 122 http://www.lenart.org.pl/

2013/4/4 Maurizio Cucchiara <mcucchiara@apache.org>:
>> My proposal would
>> be to simplify the interceptor in two ways:
>> 1) Remove the filter by cookie value: I don't know under which
>> circumstances that could be useful
> I'm not able to identify those circumstances, but AFAIU that filter is
> harmless, if you don't define a cookie value, struts will never filter
> your cookies.
> Furthermore, this change would break bacward compatibility, and this
> may make unhappy many users which know those circumstances :(.
>
>> 2) Parse the cookieName as a OGNL expression, so I can setup the cookie
>> names I want to receive dynamically, instead of harcoding them in the
>> configuration files.
> This could be useful, but at the same time there would be some
> security risk related to it.
>
>
>> Also related, there is no way in Struts to setup a Cookie.
> Actually, ATM you can implement ServletResponseAware interface. Yes, I
> know this don't mean that there is a direct way, but it is not so hard
> to implement IMHO.
>
>> I developed my
>> own CookieProviderInterceptor and CookieProvider (interfaces) to allow a=
n
>> Action to create a cookie and pass it to the CookieProviderInterceptor t=
o
>> ser it in the request, but I would love to see a more integrated process=
.
>
> At first glance, the patch you provided sounds good to me, I will get
> a deeper look in the next days.
> Further, CPI could provide remove cookie method.
>
>
> Twitter     :http://www.twitter.com/m_cucchiara
> G+          :https://plus.google.com/107903711540963855921
> Linkedin    :http://www.linkedin.com/in/mauriziocucchiara
> VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=3Dmaurizio.cucchiar=
a
>
> Maurizio Cucchiara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org