HST Request Handling

HST request handling consists of two main phases:

  1. HST Request Matching
  2. HST Request Processing

During the request matching phase, Bloomreach Content matches the hostname, portnumber, and url to a resolved sitemap item. This step determines which part of the site the request targets.

After matching, the request processing phase uses the resolved sitemap item to determine which component tree to render and which repository content to retrieve. This phase generates the final response based on the resolved configuration and content.

The following diagram outlines the overall HST request handling process. For a detailed view, download the PDF version.

HST request handling architecture from request to rendered response

Diagram:
The diagram illustrates the flow of an HTTP request through HST request handling to the HTTP response.

  • On the left, the system matches the request URL by host, context path, and sitemap item.
  • The matched sitemap item determines page and component creation, followed by rendering execution.
  • The center and top show how repository content and configuration connect to hosts, sites, configurations, sitemaps, sitemenus, and pages/components. Dotted lines indicate mappings between host names, sites, and configurations, as well as how sitemap items resolve content paths and component configuration IDs.
  • Pages are composed of layout regions such as header, body, left, middle, right, and footer.
  • On the right, components reference a component class name and templates. Example Java class code and JSP fragments illustrate layout region and body/footer rendering.
Share Feedback
Page: /build/request-handling/hst-2-request-handling
Section: Build
Category *