Octet Stream File
Content Type 'application/octet-stream' Not Supported
Upload Application Octet Stream Files

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 opened. 1 day ago Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.

MIME Content Type: application

What is MIME Application/Octet-stream?

The MIME type application/Octet-stream is considered to be one of the popular multipurpose application files. Generally this type is used for identifying the data that is not associated with any specific application. An Application/Octet-stream is a MIME attachment which is present in the operating system. This MIME type is basically related to the file extension .bin as it relates to all of the binary files. It is one of the important types in the operating system. Application/Octet-stream comes in the category of binary files. The format will be according to the coding. The working of Application/Octet-stream can be seen in web browser. So the coding will be according to the working of the web browser. Every web browser is different and gives the user various operations for use of internet. The coded information is identified by the web browser and it gives the user various options to access the MIME type.

Different applications are loaded on the system. The working of Application/Octet-stream is to identify the file which is present in the email and then scan the system. The type scans the system for suitable application that can open the data which is received in the email. To see the operation of Application/Octet-stream an example can be given. If any important letter is sent through an email the working of Application/Octet-stream can be seen in the web browser. As the data is approached and clicked for viewing, the type will scan the system for appropriate applications and give the user available options. The preferred option in this case would be of word applications as the type is a letter. If there is an extension along it's easy for the system to identify it and use it. But in some cases there is no extension given. In such situations it is the use of Application/Octet-stream types that can help.
The working of Application/Octet-stream types is done in Windows and Macintosh operating systems only. The working can be seen according to the different set ups of the type. Every application is designed in a different manner. The coding of MIME type is also done accordingly. As the data is received through email this type of MIME is used. It caters the requirements of human in sending and receiving of data through online resources. With the help of this MIME type transfer of data takes place in less time on the net. Lots of web browsers uses application/Octet-stream.

Related RFCs: [rfc2045][rfc2046]

How to fix MIME Application/Octet-stream errors?

Web browsers, like IE and Firefox, use MIME Types to determine the best host applications to render and present binary data sets that are embedded in web pages. When you encounter a MIME Application/Octet-stream error, it is caused by one of the following two types of errors:

1) You PC doesn't have a host application that can open and render MIME Application/Octet-stream content. Like file extensions, each MIME Type corresponds to a particular host application that can be used to read and write binary data sets according to the matching MIME Type specification.

2) Your PC may have errors in the Windows Registry due to corrupt and invalid entries. Even if you have a matching host application installed, it couldn't be found and used by the Internet browser.

Recommendation:

It is strongly recommended that you scan your PC to identify and correct these errors to properly view content embedded in MIME Application/Octet-stream format.

Active5 years, 8 months ago

I have a REST controller:

As you can see, I'm trying hard to specify the content type returned by the controller.

It is accessed with a REST client:

The http headers are created by a utility:

The web security configuration and code work fine. I make sure of this using a mockMvc based integration test which succeeds.

The only test that fails is the one based on the REST template:

The exception given in the Maven build console output is:

I'm using the Spring Framework 3.2.2.RELEASE version and the Spring Security 3.1.4.RELEASE version on the Java 1.6 version.

At first, I had a bare bone REST template:

I have now added to it, hoping it would help:

But it didn't change anything and the exception remains the same.

My understanding is that, it is not the REST template that needs any specific JSON configuration, but rather, that, for some reason, my controller is spitting out some application/octet-stream content type instead of some application/json content type.

Any clue?

Some additional information..

The admin rest client bean in the web test configuration:

Click your iPhone button, choose Summary This Computer Back Up Now Apply. Texting online, free website. Wait patiently as the process may last for a long time if you have too many files on your iPhone.ConclusionAs you may see, we have demonstrated how to transfer text messages from iPhone to the computer with two possible approaches in details. Then, the iPhone backup will begin. Even though iTunes is a feasible way to back up iPhone content, it has lots of limitation.

The base test class:

Rockman exe manga. The web init class:

The web configuration:

The application configuration is empty for now:

Sotirios Delimanolis

221k43 gold badges545 silver badges613 bronze badges

StephaneStephane

3,01711 gold badges57 silver badges96 bronze badges

2 Answers

I had my doubts before, but now that you've posted everything, here's what's up. Assuming the RestTemplate object you use in your getGreetingMessage() method is the same as the one declared in the @Bean method, the problem starts here

This call overwrites the default ClientHttpRequestFactory object that the RestTemplate object uses internally with a mock. In your getGreetingMessage() method, this call

doesn't actually go through the network. The RestTemplate uses the mocked ClientHttpRequestFactory to create a fake ClientHttpRequest which produces a fake ClientHttpResponse which doesn't have a Content-Type header. When the RestTemplate looks at the ClientHttpResponse to determine its Content-Type and doesn't find one, it assumes application/octet-stream by default.

So, your controller isn't setting the content type because your controller is never hit. The RestTemplate is using a default content type for your response because it is mocked and doesn't actually contain one.

From your comments:

I wonder if I understand what the mock server is testing. I understand it is to be used in acceptance testing scenario. Is it supposed to hit the controller at all ?

The javadoc for MockRestServiceServer states:

Main entry point for client-side REST testing. Used for tests that involve direct or indirect (through client code) use of the RestTemplate. Provides a way to set up fine-grained expectations on the requests that will be performed through the RestTemplate and a way to define the responses to send back removing the need for an actual running server.

In other words, it's as if your application server didn't exist. So you could throw any expectations (and actual return values) you wanted and test whatever happens from the client side

Content Type Application Octet Stream