When the application is executed, the CherryPy server is started with the
default configuration. It will listen on ``localhost`` at port ``8080``. These
-defaults can be overridden by using a configuration file or dictionary
+defaults can be overridden by using a configuration file or dictionary
Finally, the web server receives the request for the URL
mapping that is automatically generated and encoded by CherryPy; it can
be used to store session-data in a persistent cookie. For it to work you
have to enable the session functionality by setting 'tools.session.on' to
+ True in your .
* :class:`cherrypy.response <cherrypy._cprequest.Response>` contains the
data that is used to build the HTTP response.
* :attr:`cherrypy.response.headers <cherrypy.lib.httputil.HeaderMap>`
-The `cherrypy.response` object is available to affect aspects of the response
+The :class:`cherrypy.response <cherrypy._cprequest.Response>` object is
+available to affect aspects of the response
to a request. Like the request, the response object is a thread-local,
meaning although it appears to be a global variable, its value is specific
to the current thread, and thus the current request.
-CherryPy exposes the request headers (as sent from the client), and response
-headers (to be returned in the response) in the `headers` attribute of
-`cherrypy.request` and `cherrypy.response`.
+CherryPy exposes the :attr:`request headers <cherrypy.lib.httputil.HeaderMap>`
+(as sent from the client), and response headers (to be returned in the
+response) in the `headers` attribute of `cherrypy.request` and
For example, to find out what "host" to which the client intended to connect::