Generates an HTTP request and handles the response from the server.
<cfhttp url = "server URL
" charset = "character encoding
" clientCert = "filename
" clientCertPassword = "password
" columns = "query columns
" delimiter = "character
" file = "filename
" firstrowasheaders = "yes|no" getAsBinary = "auto|yes|no|never" method = "method name
" multipart = "yes|no" name = "query name
" password = "password
" path = "path
" port = "port number
" proxyServer = "host name
" proxyPort = "port number
" proxyUser = "username
" proxyPassword = "password
" redirect = "yes|no" resolveURL = "yes|no" result = "result name
" textQualifier = "character
" throwOnError = "yes|no" timeout = "time-out period in seconds" username = "username
" userAgent = "user agent
">cfhttpparam tags [optional for some methods]
</cfhttp>
cfhttpparam, GetHttpRequestData, cfftp, cfldap, cfmail, cfpop, SetEncoding
ColdFusion 8: Added the clientCert and clientCertPassword attributes.
ColdFusion MX 7.01: Added the "never" value of the getAsBinary attribute.
ColdFusion MX 7: Added the result attribute, which allows you to specify an alternate variable in which to receive a result.
ColdFusion MX 6.1:
ColdFusion MX:
The following attributes control the HTTP transaction and can be used for all HTTP methods:
Attribute |
Req/Opt |
Default |
Description |
---|---|---|---|
url |
Required |
Uses the http protocol |
Address of the resource on the server that handles the request. The URL must include the hostname or IP address. If you do not specify the transaction protocol (http:// or https://), ColdFusion uses the default protocol, http. If you specify a port number in this attribute, it overrides any port attribute value. The cfhttpparam tag URL attribute appends query string attribute-value pairs to the URL. |
charset |
Optional |
For request: UTF-8 For response: charset specified by response Content- Type header, or UTF-8 if response does not specify charset. |
The character encoding of the request, including the URL query string and form or file data, and the response. The following list includes commonly used values:
For more information character encodings, see www.w3.org/International/O-charset.html. |
clientCert |
Optional |
|
The full path to a PKCS12 format file that contains the client certificate for the request. |
clientCertPassword |
Optional |
|
Password used to decrypt the client certificate. |
getAsBinary |
Optional |
no |
ColdFusion recognizes the response body as text if:
If ColdFusion does not recognize the body as text and converts it to an object, but the body consists of text, the cfoutput tag can display it. The cfoutput tag cannot display Binary type data. (To convert binary data to text, use the ToString function.) |
method |
Optional |
GET |
|
password |
Optional |
|
Use to pass a password to the target URL for Basic Authentication. Combined with username to form a base64 encoded string that is passed in the Authenticate header. Does not provide support for Integrated Windows, NTLM, or Kerebos authentication. |
port |
Optional |
80 for http 443 for https |
Port number on the server to which to send the request. A port value in the url attribute overrides this value. |
proxyServer |
Optional |
|
Host name or IP address of a proxy server to which to send the request. |
proxyPort |
Optional |
80 |
Port number to use on the proxy server. |
proxyUser |
Optional |
|
User name to provide to the proxy server. |
proxyPassword |
Optional |
|
Password to provide to the proxy server. |
redirect |
Optional |
yes |
If the response header includes a Location field AND ColdFusion receives a 300-series (redirection) status code, specifies whether to redirect execution to the URL specified in the field:
The cfhttp.responseHeader.Location variable contains the redirection path. ColdFusion follows a maximum of four redirects on a request. If there are more, ColdFusion functions as if redirect = "no". Note: The cflocation tag generates an HTTP 302 response with the url attribute as the Location header value. |
resolveURL |
Optional |
no |
Does not resolve URLs if the file and path attributes are used. |
throwOnError |
Optional |
no |
|
timeout |
Optional |
|
Value, in seconds, that is the maximum time the request can take. If the time-out passes without a response, ColdFusion considers the request to have failed. If the client specifies a time-out in the URL search parameter (for example, ?RequestTime=120) ColdFusion uses the lesser of the URL time-out and the timeout attribute value; this ensures that the request times out before, or at the same time as, the page. If the URL does not specify a time-out, ColdFusion uses the lesser of the Administrator time-out and the timeout attribute value. If the time-out is not set in any of these, ColdFusion waits indefinitely for the cfhttp request to process. |
userAgent |
Optional |
ColdFusion |
Text to put in the user agent request header. Used to identify the request client software. Can make the ColdFusion application appear to be a browser. |
username |
Optional |
|
Use to pass a user name to the target URL for Basic Authentication. Combined with password to form a base64 encoded string that is passed in the Authenticate header. Does not provide support for Integrated Windows, NTLM, or Kerebos authentication. |
The following attribute is used with the PUT method to determine how to send data specified with httpparam type="formField":
Attribute |
Req/Opt |
Default |
Description |
---|---|---|---|
multipart |
Optional |
no (Sends as multipart only if request includes File type data.) |
Tells ColdFusion to send all data specified by cfhttpparam type="formField" tags as multipart form data, with a Content-Type of multipart/form-data. By default, ColdFusion sends cfhttp requests that contain only formField data with a Content Type of application/x-www-form-urlencoded. (If the request also includes File type data, ColdFusion uses the multipart/form-data content type for all parts.) If yes, ColdFusion also sends the request's charset in each Content-Type description. All form field data must be encoded in this character encoding, and ColdFusion does not URLEncode the data. (The field name must be in ISO-88591-1 or ASCII.) Some http parsers, including the one used by previous versions of ColdFusion, ignore the multipart form field character encoding description. |
The following attribute allows you to specify the name of the variable in which you would like the results of the operation returned. The name you specify replaces cfhttp as the prefix by which you access the returned variables. For example, if you set the result attribute to myResult, you would access FileContent as #myResult.FileContent#.
The result attribute allows functions or CFCs that are called from multiple pages at the same time to avoid overwriting the results of one call with another. For information about the variables returned by a cfhttp get operation, see Variables returned by a cfhttp get operation in the Usage section.
Attribute |
Req/Opt |
Default |
Description |
---|---|---|---|
result |
Optional |
|
Specifies the name of the variable in which you want the result returned. |
The following attributes tell ColdFusion to put the HTTP response body in a file. You can put the response body in a file for GET, POST, PUT, DELETE, OPTIONS, and TRACE methods, but it is generally not useful with the DELETE or OPTIONS method.
Attribute |
Req/Opt |
Default |
Description |
---|---|---|---|
file |
Required if path is specified and not a GET method |
See Description |
Name of the file in which to store the response body. For a GET operation, the default is the file requested in the URL, if there is one. For example, if the URL in a GET method is http:www.myco.com/test.htm, the default file is test.htm. Do not specify the path to the directory in this attribute; use the path attribute. |
path |
Required if file is specified. |
|
Tells ColdFusion to save the HTTP response body in a file. Contains the absolute path to the directory in which to store the file. |
The following attributes tell ColdFusion to convert the HTTP response body into a ColdFusion query object. They can be used with the GET and POST methods only.
Attribute |
Req/Opt |
Default |
Description |
---|---|---|---|
columns |
Optional |
First row of response contains column names. |
The column names for the query, separated by commas, with no spaces. Column names must start with a letter. The remaining characters can be letters, numbers, or underscore characters (_). If there are no column name headers in the response, specify this attribute to identify the column names. If you specify this attribute, and the firstrowasHeader attribute is True (the default), the column names specified by this attribute replace the first line of the response. You can use this behavior to replace the column names retrieved by the request with your own names. If a duplicate column heading is encountered in either this attribute or in the column names from the response, ColdFusion appends an underscore to the name to make it unique. If the number of columns specified by this attribute does not equal the number of columns in the HTTP response body, ColdFusion generates an error. |
delimiter |
Optional |
, (comma) |
A character that separates query columns. The response body must use this character to separate the query columns. |
firstrowasheaders |
Optional |
yes |
Determines how ColdFusion processes the first row of the query record set:
|
name |
Optional |
|
Tells ColdFusion to create a query object with the given name from the returned HTTP response body. |
textQualifier |
Optional |
" [double-quotation mark] |
A character that, optionally, specifies the start and end of a text column. This character must surround any text fields in the response body that contain the delimiter character as part of the field value. To include this character in column text, escape it by using two characters in place of one. For example, if the qualifier is a double-quotation mark, escape it as "". |
The cfhttp tag is a general-purpose tool for creating HTTP requests and handling the returned results. It enables you to generate most standard HTTP request types. You use embedded cfhttpparam tags to specify request headers and body content.
When ColdFusion receives a response to a cfhttp request, it can put the response body (if any) in a file or the cfhttp.FileContent string variable. If the body text is structured as a result set, ColdFusion can put the body text in query object. You can also access the values of all returned headers and specify how to handle error status and redirections, and specify a time-out to prevent requests from hanging.
The HTTP protocol is the backbone of the World Wide Web and is used for every web transaction. Because the cfhttp tag can generate most types of requests, it provides significant flexibility. Possible uses include:
This tag can, and for PUT and POST requests must, have a body that contains cfhttpparam tags. If this tag has cfhttpparam tags, it must have a </cfhttp> end tag.
To use HTTPS with the cfhttp tag, you might need to manually import the certificate for each web server into the keystore for the JRE that ColdFusion uses. This procedure should not be necessary if the certificate is signed (issued) by an authority that the JSSE (Java Secure Sockets Extension) recognizes (for example, Verisign); that is, if the signing authority is in the cacerts already. However, you might need to use the procedure if you are issuing SSL (secure sockets layer) certificates yourself.
Variables returned by a cfhttp get operation
The cfhttp tag returns the following variables. If you set the result attribute, the name you assign replaces cfhttp as the prefix. For additional information, see the result attribute.
Name |
Description |
---|---|
cfhttp.charSet |
Response character character set (character encoding) specified by the response Content-Type header. |
cfhttp.errorDetail |
If the connection to the HTTP server fails, contains details about the failure. For instance: "Unknown host: my.co.com"; otherwise, the empty string. recommends that you check this variable for an error condition before checking other variables. |
cfhttp.fileContent |
Response body; for example, the contents of a html page retrieved by a GET operation. Empty if you save the response in a file. |
cfhttp.header |
Raw response header containing all header information in a single string. Contains the same information as the cfhttp.responseHeader variable. |
cfhttp.mimeType |
MIME type specified by the response Content-Type header; for example, text/html. |
cfhttp.responseHeader |
The response headers formatted into a structure. Each element key is the header name, such as Content-Type or Status_Code. If there is more than one instance of a header type, the type values are put in an array. One common technique is to dynamically access the cfhttp.responseHeader structure as a dynamic array; for example, #cfhttp.resonseHeader[fieldVariable]#. |
cfhttp.statusCode |
The HTTP status_code header value followed by the HTTP Explanation header value; for example, "200 OK". |
cfhttp.text |
Boolean; true if the response body content type is text. ColdFusion recognizes the response body as text in the following situations:
|
Building a query from a delimited text file
The cfhttp tag can create a ColdFusion query object form the response body. To do so, the response body must consist of lines of text, with each line having fields that are delimited by a character that identifies the column breaks. The default delimiter is a comma (,). The response data can also use a text qualifier; the default is a double-quotation mark ("). If you surround a string field in the text qualifier, the field can contain the delimiter character. To include the text qualifier in field text, escape it by using a double character. The following line shows a two-line request body that is converted into a query. It has three comma-delimited fields:
Field1,Field2,Field3 "A comma, in text","A quote: ""Oh My!""",Plain text
Run the following code to show how ColdFusion treats this data:
<cfhttp method="Get" url="127.0.0.1:8500/tests/escapetest.txt" name="onerow"> <cfdump var="#onerow#"><br>
Column names can be specified in three ways:
The cfhttp tag checks to ensure that column names in the data returned by the tag start with a letter and contain only letters, numbers, and underscore characters (_).
ColdFusion checks for invalid column names. Column names must start with a letter. The remaining characters can be letters, numbers, or underscores (_). If a column name is not valid, ColdFusion generates an error.
<!--- This example displays the information provided by the Designer & Developer Center XML feed, http://www..com/desdev/resources/_resources.xml See http://www..com/desdev/articles/xml_resource_feed.html for more information on this feed. ---> <!--- Set the URL address. ---> <cfset urlAddress="http://www..com/desdev/resources/_resources.xml"> <!--- Use the CFHTTP tag to get the file content represented by urladdress. Note that />, not an end tag, terminates this tag. ---> <cfhttp url="#urladdress#" method="GET" resolveurl="Yes" throwOnError="Yes"/> <!--- Parse the XML and output a list of resources. ---> <cfset xmlDoc = XmlParse(CFHTTP.FileContent)> <!--- Get the array of resource elements, the xmlChildren of the xmlroot. ---> <cfset resources=xmlDoc.xmlroot.xmlChildren> <cfset numresources=ArrayLen(resources)> <cfloop index="i" from="1" to="#numresources#"> <cfset item=resources[i]> <cfoutput> <strong><a href=#item.url.xmltext#>#item.title.xmltext#</strong></a><br> <strong>Author</strong> #item.author.xmltext#<br> <strong>Applies to these products</strong><br> <cfloop index="i" from="4" to="#arraylen(item.xmlChildren)#"> #item.xmlChildren[i].xmlAttributes.Name#<br> </cfloop> <br> </cfoutput> </cfloop>