[ZCM] [ZC] 958/ 4 Comment "Browser ID Manager cookie name problem"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #958 Update (Comment) "Browser ID Manager cookie name problem"
 Status Pending, Zope/bug low
To followup, visit:
  http://zope.org/Collectors/Zope/958

==============================================================
= Comment - Entry #4 by pdreuw on Aug 2, 2004 2:00 pm

I did this using Zope 2.6.2. I did not test that with newer versions.

step1: place a browser_id_manager in your test application folder and change the entry "Browser id name" in the browser_id_manager page to a desired name. 

step1b: add a session_data_manager with session_data etc. in the test app folder (and as i did the CookieCrumbler)

step2: build a page template with code that reads some SESSION data

step3: build a python func (in ZMI) that reads or manipulates the SESSION data

step4: glue that together with some nice HTML forms - actually the SESSION was meant to transport  form data from multiple forms to the last form. Each form calls a python script that fills the data from thle last form into the SESSION data and calls the next TAL HTML form and so on till the last form is reached an a summary is shown (as zpt) 

This works fine as long as you don´t change the Browser id name. If you do, Zope places two Cookies into the browser and creates two SESSION objects. The zpt forms (which in my example show some of the entered data of the prev. forms) see the one SESSION data, the python scripts see the other SESSION data. 

I consider this a bug. I did not any more research on that, I simply let the name unchanged and that´s it. (But that´s a workaround..) Again, I did that on Zope 2.6.2.




________________________________________
= Comment - Entry #3 by mcdonc on May 17, 2004 4:41 am

I cannot replicate this behavior.  Can you provide a set of steps that would allow me to do so?
________________________________________
= Comment - Entry #2 by pdreuw on Jun 27, 2003 5:08 pm

I forgot to say, the used browser got both cookies , one with the name "_ZopeId" and one with the entered ID. Both cookies expire after browser session, this all happens with Mozilla as well as IE 6.0.
________________________________________
= Request - Entry #1 by Anonymous User on Jun 27, 2003 4:53 pm

Zope Session management works fine as long as you change the cookie name in the browser id manager. 
If I change the cookies name, I got two different session data records, one usable in python scripts refering to a session derived from a still set cookie named "_ZopeId" an another session data record referenced to a cookie named as I wanted. This session is used in my page templates. This behavior is not wanted by me, I wanted one session data record, accessable from both, python as well as TAL. This I only get leaving the cookies name untouched .
==============================================================