cfhttptag/construct (https://cfdocs.org/cfhttp). The
cfhttpcall will generate an HTTP/S request and parse the response into a nice CFML structure.
cfhttpparamconstruct. This parameter can be of many different types:
header, body, xml, cgi, file, url, formfield, cookiedepending on the requirements of the http endpoint.
cfhttpparamconstruct to pass parameters to the http/s endpoint. The parameters can be of different types as we can see in the following table.
valueis the body of the HTTP request.
text/xmland specifies that the
valueattribute contains the body of the HTTP request.
headerbut URL encodes the
filetype; ignored for all other types. The absolute path to the file that is sent with the request.
filetype; invalid for all other types. Specifies the MIME media type of the file contents. The content type can include an identifier for the character encoding of the file; for example, text/html; charset=ISO-8859-1 indicates that the file is HTML text in the ISO Latin-1 character encoding.
cfhttp. Each implementation was mostly the same but slightly different. It was additionally frustrating because I really only needed to tweak a few values, usually just the
Authorizationheader. It would be nice to create an HTTP client pre-configured for each of these SDK's. It seemed the perfect fit for a module.
HyperBuilder. This is commonly aliased as
HyperBuildercreates new requests. This can be done in one of two ways:
newmethod will create a new request with the configured defaults.
HyperBuilderinstance will create a new request and forward on the method call.
HyperBuilderlets you easily create requests with defaults while also avoiding having to deal with providers directly.
HyperBuilderis the component you will most likely inject,
HyperRequestis the component will you interact with the most.
HyperRequestprovides a fluent interface to configure your HTTP call.
HyperBuilderinstance. The easiest way to do this is to configure it in WireBox:
initmethod or by calling the appropriate
HyperRequestmethod on the