Tracking strategy for default identifier

Hi all,

I recently moved to `WACookieForBrowserIPForCrawlerTrackingStrategy`
tracking strategy, but I noticed that the session count was increasing
beyond the actual "normal" use, suggesting a new session was being
created everytime.

Then I noticed that when I perform a request to the default
dispatcher, it creates a new session, because the cookie is created
with the app path so the browser is not sending it back when visiting
the root.

I have the default name for the dispatcher as:
WAAdmin defaultDispatcher defaultName: 'app'.

If I visit this:
http://localhost:8080/app
I get a new cookie (if needed) and subsequent requests don't create a new one.

If I visit
http://localhost:8080/
I get a new cookie (and a new session is created) each time because
the cookie is created with the `/app` path.

Did this happen to anyone else?

Regards!

Esteban A. Maringolo
_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside