HttpRequest

This topic is a work in progress

Think of HttpRequest as a template for creating an HttpRequestMessage.

At its heart, it is a collection of configuration actions (and any data required to support those actions) that are invoked against each outgoing request message.

Because its functionality is expressed in terms of actions, it is trivially easy to write your own domain-specific extensions for HttpRequest (see the section on extensibility for details).

A powerful feature of HTTPlease is that the data used by those actions is resolved at the time each outgoing HttpRequestMessage is created (rather than when the HttpRequest template is created).

This enables each HttpRequest to be immutable; each change (or sequence of changes) to the HttpRequest produces a new HttpRequest that only captures the differences from the previous HttpRequest.

HttpRequest uses an ImmutableDictionary to store its properties.

• Usage
  • Creating a request from a URI
  • Binding request parameters
  • Binding request parameters to an object’s properties
  • Creating a request with late-bound parameters
  • Working with responses