Commits

daveschaefer committed 6b2b222

Docs: Add more internal links

  • Participants
  • Parent commits 5aa08db

Comments (0)

Files changed (2)

sphinx/source/tutorial/basics.rst

 
 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 :doc:`configuration file </tutorial/config>` or dictionary
 (more on this later).
 
 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 config.
+   True in your :doc:`config </tutorial/config>`.
  * :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>`
 CherryPy Response
 -----------------
 
-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.
 HTTP Headers
 ------------
 
-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
+`cherrypy.response`.
 
 For example, to find out what "host" to which the client intended to connect::
 

sphinx/source/tutorial/engine.rst

  * :class:`Autoreloader<cherrypy.process.plugins.Autoreloader>` (off in the "production" :ref:`environment<environments>`)
  * :class:`cherrypy.server<cherrypy._cpserver.Server>`
  * :class:`cherrypy.checker<cherrypy._cpchecker.Checker>`
- * Engine log messages go to :class:`cherrypy.log<cherrypy._GlobalLogManager>`.
+ * :doc:`Engine log messages </refman/_cplogging>` go to :class:`cherrypy.log<cherrypy._GlobalLogManager>`.
  * A :class:`Signal Handler<cherrypy.process.plugins.SignalHandler>`.