Serving HTTP and other protocols

Serving content from your site to your users is effectively a mechanism to generate HTTP responses to HTTP requests.

In Plone, answering to HTTP requests can be divided to three subproblems:

• managing the lifecycle of the HTTP request and response pair;
• publishing, by traversing the request to the target object by its URI;
• choosing different parts of the code depending on active layers.

Plone and Zope 2 application servers support FTP, WebDAV and XML-RPC protocols besides plain HTTP.

• HTTP request and response
  • Introduction
  • Lifecycle
  • Webservers
  • HTTP Request
  • Accessing HTTP request outside context
  • HTTP response
  • Middleware-like hooks
  • Transform chain
  • Post-publication hook
  • Custom redirect mappings
  • Cross-origin resource sharing (CORS)
• Traversing
  • Introduction
  • Object ids
  • Exploring Zope application server
  • Attribute traversing
  • Container traversing
  • Traversing by full path
  • Getting the object path
  • Getting object URL
  • Getting the parent
  • Getting the site root
  • Getting Zope application server handle
  • Acquisition effect
  • Defaut content item
  • Custom traversal
  • Traverse events
  • Advanced traversing with search conditions
  • Other resources
• Publishing
  • Example publishers
• XML-RPC
  • Introduction
  • Authentication
  • ZPublisher client
  • Web Services API for Plone (wsapi4plone)
  • More information
• WebDAV
  • Introduction
  • Supporting WebDAV in your custom content
  • WebDAV notes
• FTP
  • Enabling FTP