How EZcomm protocol determines whether an inbound payload is "text" or "binary".

How EZcomm protocol determines whether an inbound payload is "text" or "binary".

book

Article ID: KB0094339

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect -
Not Applicable -

Description

Resolution:
Description:
============
How Ezcomm protocol determines whether an inbound payload is "text" or "binary".

Environment:
============
BusinessConnect EZcomm Protocol

Symptoms:
=========

Cause:
======
BC treats the inbound payload as binary if the "Content-type" in the MIME header is set to "application/octet stream" as shown below:

------=_Part_265_1758317315.1315550611433
Content-Type: application/octet-stream; name="N/A"
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename="N/A"


Resolution:
===========
If you would like BC to treat the inbound payload as text, have your trading partner change the "Content-Type" to "text" (i.e. "text/plain", "text/xml").

Issue/Introduction

How EZcomm protocol determines whether an inbound payload is "text" or "binary".