rbf_sendHttpRequest

rbf_sendHttpRequest(url, method, headers, params, body, options)			
			

<script>
  function processExchangeRates(resp) {
      if (resp.status == 200) {
          var node = $.parseXML(resp.body); //parse xml string literal
          var currRate = $(node).find('Rate').text();
      }
  }

  rbf_sendHttpRequest('http://query.yahooapis.com/v1/public/yql', //url
      'GET', //http method
      {
          'Accept': 'text/xml'
      }, // headers
      {
          'q': 'select * from yahoo.finance.xchange where pair in ("USDEUR")',
          'env': 'store://datatables.org/alltableswithkeys'
      }, // params
      null, //body
      {
          callback: processExchangeRates
      } //options
  );
</script>			
			

Support for Base64 Encoding of Binary HTTP Responses

Binary Response Handling (Base64 Encoding)

Previously, all HTTP APIs within the platform returned strings. When remote endpoints sent binary content, converting bytes to text corrupted the data, complicating file downloads and input to binary field APIs requiring Base64.

The Infinite Blue Platform HTTP APIs now support binary and other non-text response types via an optional request header. This enhancement prevents data corruption when processing files such as PDFs, Excel, Word documents, or images.

All HTTP APIs now accept this optional request header:

When this header is included in the request:

• The API reads the response body as raw bytes.

• The API returns a Base64-encoded string of those bytes instead of decoding the content as text.

• The returned Base64 value is compatible with existing binaryField API methods.

When the header is not included, all APIs behave as they do currently, returning responses as plain text strings.

Example (Server-Side JavaScript)

Downloading a PDF and saving it to a binary field:

var url = "{!DownloadURL}";

var method = "GET";

var headers = {

"Content-Type": "application/pdf",

"Content-Transfer-Encoding": "base64"

};

var params = null;

var body = null;

var options = null;

var resp = rbv_api.sendHttpRequest(url, method, headers, params, body, options);

// With Content-Transfer-Encoding=base64,

// resp.body contains a Base64-encoded string of the PDF bytes.

if (resp && resp.body) {

var fileName = Date.now() + "." + "{!File_Extension}";

rbv_api.setBinaryFieldValue(

"pdftestobj",

{!id},

"fu1",

resp.body,               // Base64 content returned from HTTP API

"application/pdf",

fileName

);

}

Header value matching is performed in a case-insensitive manner.

Only the response body is subject to modification. Status codes, headers, and associated metadata remain unchanged.

Scripts and integrations that do not transmit the Content-Transfer-Encoding: base64 header maintain compatibility.