Rogue Wave banner
Previous fileTop of DocumentContentsIndex pageNext file
HydraExpress Servlet Development Guide

7.2 Understanding Request Routing

When the servlet container receives an incoming message, it parses the message and constructs a request object and a response object. The container uses the URL in the request to determine the destination for the request — either a servlet, or a static file in one of the container contexts. If the destination is a servlet, the container builds a filter chain for any filters that match the location of the servlet. The container then forwards the request and response as follows:

Consider a third-party container that holds an examples context and a servlet at /HelloWorldExample within that context. The container uses an AJP13 connection to an external Web server that is configured to forward requests for /examples to the HydraExpress Agent. When the external Web server receives the HTTP/1.1 request below.

the Web server encodes the request into AJP13 format and forwards the request to the Agent. The Agent receives the request and extracts the location from the request. The Agent matches /examples to the examples context, then matches the path /HelloWorldExample within the examples context.



Previous fileTop of DocumentContentsNo linkNext file

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo are registered trademarks of Rogue Wave Software, and HydraExpress is a trademark of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.