The request object encapsulates all of the information regarding the current request in Zope. This includes, the input headers, form data, server data, and cookies.
The request object is a mapping object that represents a collection of variable to value mappings. In addition, variables are divided into five categories:
These variables include input headers, server data, and other request-related data. The variable names are as specified in the CGI specification
These are data extracted from either a URL-encoded query string or body, if present.
These are the cookie data, if present.
These are callables which are deferred until explicitly referenced, at which point they are resolved (called) and the result stored as "other" data, ie regular request data.
Thus, they are "lazy" data items. An example is SESSION objects.
Lazy data in the request may only be set by the Python method set_lazy(name,callable) on the REQUEST object. This method is not callable from DTML or through the web.
Data that may be set by an application object.
The request object may be used as a mapping object, in which case values will be looked up in the order: environment variables, other variables, form data, and then cookies.
These special variables are set in the Request:
PARENTS
PARENTS[0]
would be the ancestor of
the published object.REQUEST
RESPONSE
PUBLISHED
URL
URL0
is the same as URL
. URL1
is the same as
URL0
with the last path element removed. URL2
is the same
as URL1
with the last element removed. Etcetera. For example if URL=http://localhost/foo/bar
, then
URL1=http://localhost/foo
and URL2=http://localhost
.
URLPATH0
is the path portion of URL
,
URLPATH1
is the path portion of URL1
, and so on. For example if URL=http://localhost/foo/bar
, then
URLPATH1=/foo
and URLPATH2=/
.
BASE0
is the URL up to but not including the Zope
application object. BASE1
is the URL of the Zope application
object. BASE2
is the URL of the Zope application object with
an additional path element added in the path to the published
object. Etcetera. For example if URL=http://localhost/Zope.cgi/foo/bar
, then
BASE0=http://localhost
, BASE1=http://localhost/Zope.cgi
,
and BASE2=http://localhost/Zope.cgi/foo
.
BASEPATH0
is the path portion of BASE0
,
BASEPATH1
is the path portion of BASE1
, and so on.
BASEPATH1
is the externally visible path to the root Zope
folder, equivalent to CGI's SCRIPT_NAME
, but virtual-host aware. For example if URL=http://localhost/Zope.cgi/foo/bar
, then
BASEPATH0='/, BASEPATH1=
/Zope.cgi', and BASEPATH2=/Zope.cgi/foo
.
Create a new name in the REQUEST object and assign it a value.
This name and value is stored in the Other
category.
Returns a sorted sequence of all keys in the REQUEST object.
Returns a sequence of (key, value) tuples for all the keys in the REQUEST object.
Sets the specified elements of SERVER_URL
, also affecting
URL
, URLn
, BASEn
, and absolute_url()
.
Provides virtual hosting support.
Returns a true value if the REQUEST object contains key, returns a false value otherwise.
Returns a sequence of values for all the keys in the REQUEST object.
Alters URL
, URLn
, URLPATHn
, BASEn
, BASEPATHn
, and
absolute_url()
so that the current object has path path
.
If hard
is true, PARENTS
is emptied.
Provides virtual hosting support. Intended to be called from publishing traversal hooks.
Returns information about the request as text. This is useful for debugging purposes. The returned text lists form contents, cookies, special variables, and evironment variables.
Return the named HTTP header, or an optional default argument
or None if the header is not found. Note that both original
and CGI header names without the leading HTTP_
are
recognized, for example, Content-Type
, CONTENT_TYPE
and
HTTP_CONTENT_TYPE
should all return the Content-Type header,
if available.