[Seaside] [2.8]Back button, new sessions and forcing s and kkeys in the initial URL

Boris Popov boris at deepcovelabs.com
Wed Jun 24 22:12:27 UTC 2009

Also, you _can_ find client IP as per,





 | req |
 req := self currentRequest.
   headerAt: 'x-forwarded-for'
   ifAbsent: [req nativeRequest remoteAddress].

Hope this helps,


DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message header.
Unless otherwise indicated, it contains information that is private and
confidential. If you have received it in error, please notify the sender
and delete the entire message including any attachments.

Thank you. 

-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Michael
Sent: Wednesday, June 24, 2009 3:10 PM
To: Seaside - general discussion
Subject: Re: [Seaside] [2.8]Back button, new sessions and forcing s and
kkeys in the initial URL

Carl Gundel wrote:
> I'm writing an A/B testing framework in Seaside.  All is going very 
> well except that I've discovered if a visitor to the site being tested

> hits the back button all the way back to the initial page then there 
> is no s key in the URL, so Seaside makes a new session.  This will 
> cause my visitor click tracking to lose track.  It wouldn't be a big 
> problem if I were able to get the visitor's IP address, but I can't 
> because this server will be proxied behind Apache.
> So, is there any way I can force the initial page view to have the s 
> and k keys?
Make your initial page a WATask which calls your first WAComponent.

seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list