Exception in thread main org.apache.solr.client.solrj.impl.HttpSolrServerRemoteSolrException: Expected mime type application/octet-stream but got text/html. html head meta http-equiv Content-Type contenttext/htmlcharset After much pain this now basically works except nginx always returns the file with text/ html content type. The default content type is application/octet-stream, specified in the http block. Last Modified: 2014-03-08. Browser passes content-type as application/ octet-stream. I have a JSP page with a file selector.COBOLdinosaur(2 comments). LVL 53. HTML30. JSP3. Java EE2. It looks like you are serving xml and xml.gz files with a content-type of text/ html on rpm.nodesource.com. This breaks rpm repository clients that expect a content-type of application/octet-stream. About "application/octet-stream" MIME attachments.
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 in an application, such as a spreadsheet or word processor. I played around with other content types like text/html and text/xml but I still got null.A Content-Type of application/octet-stream is unknown to Slim and so it cannot decode the data. Im using an html input control (System.web.UI.HTMLControls.