Known Indirect Subclasses
||Default implementation of
||HTTP protocol processor is a collection of protocol interceptors that
implements the 'Chain of Responsibility' pattern, where each individual
protocol interceptor is expected to work on a particular aspect of the HTTP
protocol the interceptor is responsible for.
||RequestConnControl is responsible for adding
to the outgoing requests, which is essential for managing persistence of
||RequestContent is the most important interceptor for outgoing requests.
||RequestDate interceptor is responsible for adding
to the outgoing requests This interceptor is optional for client side
||RequestExpectContinue is responsible for enabling the 'expect-continue'
handshake by adding
||RequestTargetHost is responsible for adding
||RequestUserAgent is responsible for adding
HTTP protocol interceptor is a routine that implements a specific aspect of
the HTTP protocol. Usually protocol interceptors are expected to act upon
one specific header or a group of related headers of the incoming message
or populate the outgoing message with one specific header or a group of
Protocol Interceptors can also manipulate content entities enclosed with messages.
Usually this is accomplished by using the 'Decorator' pattern where a wrapper
entity class is used to decorate the original entity.
Protocol interceptors must be implemented as thread-safe. Similarly to
servlets, protocol interceptors should not use instance variables unless
access to those variables is synchronized.
(HttpRequest request, HttpContext context)
Processes a request.
On the client side, this step is performed before the request is
sent to the server. On the server side, this step is performed
on incoming messages before the message body is evaluated.
||the request to preprocess
||the context for the request