Commit bd9013f6 authored by matt@zope.com's avatar matt@zope.com

Added files I forgot to add earlier ;)

parent 4373512d
Browser Id Manager - Change
Form options available are:
browser id mgr on -- check to activate this Browser Id Manager,
uncheck to disable it.
title -- the browser id manager title.
session token key -- the cookie name and/or form variable name
used for this browser id manager instance. This will be the
name looked up in the 'cookies' or 'form' REQUEST namespaces
when the browser id manager attempts to find a cookie or form
variable with a session token in it.
token key search namespaces -- choose a "priority" for each
token key namespace. A priority of "1" is highest. For
instance, setting 'cookies' to '1' and 'form vars' to '2'
means that the browser id manager checks for cookies with a
session token first, then form variables second. Choosing
"off" for either 'cookies' or 'form vars' entirely excludes
that namespace from being searched for a session token. The
namepace identifiers ('cookies' and 'form') refer to the
REQUEST namespaces searched for the token key
(ie. REQUEST.cookies, REQUEST.form).
cookie path -- this is the 'path' element which should be sent
in the session token cookie. For more information, see the
Netscape Cookie specification at
http://home.netscape.com/newsref/std/cookie_spec.html.
cookie domain -- this is the "domain" element which should be
sent in the session token cookie. For more information, see
the Netscape Cookie specification at
http://home.netscape.com/newsref/std/cookie_spec.html.
Leaving this form element blank results in no domain element
in the cookie. If you change the cookie domain here, the
value you enter must have at least two dots (as per the cookie
spec).
cookie lifetime in days -- browser id cookies sent to browsers
will last this many days on a remote system before expiring if
this value is set. If this value is 0, cookies will persist
on client browsers for only as long as the browser is open.
only send cookie over https -- if this flag is set, only send
cookies to remote browsers if they're communicating with us
over https. The browser id cookie sent under this
circumstance will also have the 'secure' flag set in it, which
the remote browser should interpret as a request to refrain
from sending the cookie back to the server over an insecure
(non-https) connection. NOTE: In the case you wish to share
browser id cookies between https and non-https connections
from the same browser, do not set this flag.
After reviewing and changing these options, click the "Change"
button to change the browser id manager.
See Also
- "Session Tracking":Sessions.stx
- "Session Administration":session-admin.stx
Session Data Manager - Change
The session data manager add form displays these options:
title -- choose a title for the session data manager
transient object container path --
the path in Zope to a transient object container which will
store the actual session data. This path is
/temp_folder/transient_container in a default Zope installation.
automatic SESSION placement in REQUEST object --
check this option to have a SESSION object automatically
inserted into the REQUEST object, corresponding to the
current browser's session.
After reviewing and changing these options, click the "Change"
button to change the session data manager.
See Also
- "Session Tracking":Sessions.stx
- "Session Administration":session-admin.stx
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment