![Octet stream encoding](https://kumkoniak.com/16.jpg)
![octet stream encoding octet stream encoding](https://alexisfraser.com/pictures/how-to-convert-application-octet-stream-to-text-plain-3.png)
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. 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. 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. 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. In any case I decided the better path was to produce local parquet files instead and shift those to azure saving the computation costs of conversion in the cloud.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. It does seem odd there is no support for that format because extracting compressed json data from sql server instead of streaming uncompressed data makes a lot of sense. The only thing I noticed when opening the json file after decompressing it, the file is not in txt format its an octet stream which might be this bom format you are referring to. The Azure blob client can accept that stream and uploads the file to a blob. If its a case of this process creating a utf8 bom format then can I suggest support for this be added because this is a very good way to extract large amounts of data from sql server in a compressed format using streams and not any data table that consumes memory. net client issues this query with the reader issuing a get stream. it's a query issues to sql server wrapping a for json query in a sql compress command. I am unsure what format it is because there is nowhere to specify the format.
![Octet stream encoding](https://kumkoniak.com/16.jpg)