I have an issue with data coming from the internet. I have a package coming from the internet that has the content-type:application/octet-stream.

My question is how do i decode it to readable values (such as 1,4.321,-2.6013 etc)? or is there any application that can do this?

• Content type 'application/octet-stream' will always cause Firefox to show the 'open with' download dialog. To avoid this download you would have to configure the.
• That content type does not indicate any encoding.All it means is that the data represents a stream of (8-bit) bytes. How they're encoded is an entirely separate matter.

Dec 20, 2017 - A MIME attachment with the content type 'application/octet-stream' is a binary file. Typically, it will be an application or a document that must be.

For example:

3ecccccd is 0.400 (http://gregstoll.dyndns.org/~gregstoll/floattohex/) some are real numbers. 07d0 is 2.000

2 Answers

HTTP's Content-Encoding header only applies to how data is encoded inside of the HTTP message itself, not how the data itself is encoded outside of HTTP. There is no Content-Encoding header present in your example, so HTTP is not encoding the data in any way, it is giving you the raw data as-is.

When HTTP's Content-Type header is application/octet-stream, that mean the data (after decoding it based on the Content-Encoding, if any) is raw 8bit data, the sender does not know what the actual type of the data is. Without a more meaningful Content-Type to tell you what the data actually represents, the only thing you can do is analyze the raw data and make educated guesses about what it might be, unless you know through other means what the data is supposed to be.

Usually, binary data formats have a header/signature at the front of the data to identify what the data is, so you might start with that.

Until you can identify the data type, you cannot know which bytes represent what kind of values, what endian is used for multi-byte values, etc. In short, you need more information about the data you are downloading in order to know how to process it.

That content type does not indicate any encoding. All it means is that the data represents a stream of (8-bit) bytes. How they're encoded is an entirely separate matter. To discover the encoding, you can look at other headers (such as Content-Encoding), or else the encoding might be implicit, in which case you'll need to consult documentation. Then choose an appropriate decoding strategy based on that.

Not the answer you're looking for? Browse other questions tagged androidcwindowsdelphiweb or ask your own question.

Various content types can flow through a logic app,for example, JSON, XML, flat files, and binary data.While Logic Apps supports all content types, some have nativesupport and don't require casting or conversion in your logic apps.Other types might require casting or conversion as necessary.This article describes how Logic Apps handles content types andhow you can correctly cast or convert these types when necessary.

To determine the appropriate way for handling content types,Logic Apps relies on the Content-Type header value in HTTP calls,for example:

• application/json (native type)
• text/plain (native type)

application/json

Logic Apps stores and handles any request with the application/jsoncontent type as a JavaScript Notation (JSON) object.By default, you can parse JSON content without any casting.To parse a request that has a header with the 'application/json' content type,you can use an expression. This example returns the value dog from theanimal-type array without casting:

@body('myAction')['animal-type'][0]

If you're working with JSON data that doesn't specify a header,you can manually cast that data to JSON by using thejson() function,for example:

@json(triggerBody())['animal-type']

Create tokens for JSON properties

Logic Apps provides the capability for you to generate user-friendlytokens that represent the properties in JSON content so you canreference and use those properties more easily in your logic app's workflow.

• Request trigger

  When you use this trigger in the Logic App Designer, you can providea JSON schema that describes the payload you expect to receive.The designer parses JSON content by using this schema and generatesuser-friendly tokens that represent the properties in your JSON content.You can then easily reference and use those properties throughout yourlogic app's workflow.

  If you don't have a schema, you can generate the schema.

  1. In the Request trigger, select Use sample payload to generate schema.

  2. Under Enter or paste a sample JSON payload, provide a sample payloadand then choose Done. For example:

     The generated schema now appears in your trigger.

     Here is the underlying definition for your Request trigger in the code view editor:

  3. In your request, make sure you include a Content-Type headerand set the header's value to application/json.

• Parse JSON action

  When you use this action in the Logic App Designer,you can parse JSON output and generate user-friendlytokens that represent the properties in your JSON content.You can then easily reference and use those propertiesthroughout your logic app's workflow. Similar tothe Request trigger, you can provide or generate aJSON schema that describes the JSON content you want to parse.That way, you can more easily consume data from Azure Service Bus,Azure Cosmos DB, and so on.

text/plain

When your logic app receives HTTP messages thathave the Content-Type header set to text/plain,your logic app stores those messages in raw form.If you include these messages in subsequent actions without casting,requests go out with the Content-Type header set to text/plain.

For example, when you're working with a flat file,you might get an HTTP request with the Content-Typeheader set to text/plain content type: Activation key for windows 7.

Date,Name,Address
Oct-1,Frank,123 Ave

If you then send this request on in a later action as the body for another request,for example, @body('flatfile'), that second request also has a Content-Typeheader that's set to text/plain. If you're working with data that is plain textbut didn't specify a header, you can manually cast that data to text by using thestring() functionsuch as this expression:

@string(triggerBody())

application/xml and application/octet-stream

Logic Apps always preserves the Content-Type in a received HTTP request or response.So if your logic app receives content with Content-Type set to application/octet-stream,and you include that content in a later action without casting,the outgoing request also has Content-Type set to application/octet-stream.That way, Logic Apps can guarantee that data doesn't get lost while moving through the workflow.However, the action state, or inputs and outputs, is stored in a JSON objectwhile the state moves through the workflow.

Converter functions

To preserve some data types, Logic Apps converts content to a binarybase64-encoded string with appropriate metadata that preserves boththe $content payload and the $content-type, which are automatically converted.

This list describes how Logic Apps converts content when you use thesefunctions:

• json(): Casts data to application/json
• xml(): Casts data to application/xml
• binary(): Casts data to application/octet-stream
• string(): Casts data to text/plain
• base64(): Converts content to a base64 string
• base64toString(): Converts a base64 encoded string to text/plain
• base64toBinary(): Converts a base64 encoded string to application/octet-stream
• encodeDataUri(): Encodes a string as a dataUri byte array
• decodeDataUri(): Decodes a dataUri into a byte array

For example, if you receive an HTTP requestwhere Content-Type set to application/xml,such as this content: Tv theme songs download free.

You can cast this content by using the @xml(triggerBody())expression with the xml() and triggerBody() functionsand then use this content later. Or, you can use the@xpath(xml(triggerBody()), '/CustomerName') expressionwith the xpath() and xml() functions.

Other content types

Logic Apps works with and supports other content types,but might require that you manually get the messagebody by decoding the $content variable.

For example, suppose your logic app gets triggered by a requestwith the application/x-www-url-formencoded content type.To preserve all the data, the $content variable in therequest body has a payload that's encoded as a base64 string:

CustomerName=Frank&Address=123+Avenue

Because the request isn't plain text or JSON,the request is stored in the action as follows:

Logic Apps provides native functions for handling form data, for example:

Or, you can manually access the data by using an expression such as this example:

@string(body('formdataAction'))

If you wanted the outgoing request to have the sameapplication/x-www-url-formencoded content type header,you can add the request to the action's body withoutany casting by using an expression such as @body('formdataAction').However, this method only works when the body is the onlyparameter in the body input. If you try to use the@body('formdataAction') expression in an application/json request,you get a runtime error because the body is sent encoded.