You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Angelo Chen <an...@yahoo.com.hk> on 2008/10/10 13:35:34 UTC
Re: T5, SEO & and Stripping JSession Id effects
Hi Howard,
Is this option already implemented? I need to strip the session id in the
URLs.
Howard Lewis Ship wrote:
>
> Tapestry could add an option to NOT encode the session id into URLs,
> with the caveat that clients with cookies disabled would see degraded
> or non-functional behavior. Anyway, it's one of the advantages of
> having all URLs generated through a single piece of code.
>
> On Wed, Mar 5, 2008 at 11:42 AM, Filip S. Adamsen <fs...@fsadev.com> wrote:
>> Hi,
>>
>> I've been running a production application with a servlet filter that
>> strips the jsessionid for a couple of weeks now and everything's been
>> fine so far.
>>
>> -Filip
>>
>> Daniel Leffel skrev:
>>
>>
>> > Hi,
>> > We're in the process of developing a webapp using T5. The site
>> leverages
>> > session persistence on many pages, including a number of pages
>> important for
>> > the natural search content. It seems to us that levering a filter to
>> strip
>> > the jessionid from non-cookie enabled user agents would be an
>> effective way
>> > to keep jsessionids from popping up in the url. Other than insuring
>> all
>> > pages gracefully handle sessions which are effectively stateless (from
>> > non-cookied enabled user agents), are there any other concerns we
>> should be
>> > thinking about?
>> >
>> > Danny
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/T5%2C-SEO---and-Stripping-JSession-Id-effects-tp15843860p19916616.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5, SEO & and Stripping JSession Id effects
Posted by Massimo Lusetti <ml...@gmail.com>.
On Fri, Oct 10, 2008 at 3:41 PM, Andreas Andreou <an...@gmail.com> wrote:
> just add a filter like the one described at:
> http://randomcoder.com/articles/jsessionid-considered-harmful
A ServletFilter can do it but a T5 RequestFilter or Dispatcher can do
it too without have you to deal with Servlet spec.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5, SEO & and Stripping JSession Id effects
Posted by Andreas Andreou <an...@gmail.com>.
just add a filter like the one described at:
http://randomcoder.com/articles/jsessionid-considered-harmful
On Fri, Oct 10, 2008 at 2:35 PM, Angelo Chen <an...@yahoo.com.hk> wrote:
>
> Hi Howard,
>
> Is this option already implemented? I need to strip the session id in the
> URLs.
>
>
> Howard Lewis Ship wrote:
>>
>> Tapestry could add an option to NOT encode the session id into URLs,
>> with the caveat that clients with cookies disabled would see degraded
>> or non-functional behavior. Anyway, it's one of the advantages of
>> having all URLs generated through a single piece of code.
>>
>> On Wed, Mar 5, 2008 at 11:42 AM, Filip S. Adamsen <fs...@fsadev.com> wrote:
>>> Hi,
>>>
>>> I've been running a production application with a servlet filter that
>>> strips the jsessionid for a couple of weeks now and everything's been
>>> fine so far.
>>>
>>> -Filip
>>>
>>> Daniel Leffel skrev:
>>>
>>>
>>> > Hi,
>>> > We're in the process of developing a webapp using T5. The site
>>> leverages
>>> > session persistence on many pages, including a number of pages
>>> important for
>>> > the natural search content. It seems to us that levering a filter to
>>> strip
>>> > the jessionid from non-cookie enabled user agents would be an
>>> effective way
>>> > to keep jsessionids from popping up in the url. Other than insuring
>>> all
>>> > pages gracefully handle sessions which are effectively stateless (from
>>> > non-cookied enabled user agents), are there any other concerns we
>>> should be
>>> > thinking about?
>>> >
>>> > Danny
>>> >
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/T5%2C-SEO---and-Stripping-JSession-Id-effects-tp15843860p19916616.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org