"Signed exchange response without "X-Content-Type-Options: nosniff" header is not supported." is logged in Google Chrome console logs when calling a REST service implemented using TIBCO ActiveMatrix BusinessWorks Plug-in for REST and JSON Software
Article ID: KB0077381
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for REST and JSON | 2.1.0 |
Description
When Google Chrome 73.x or higher is used to call a REST service implemented using TIBCO ActiveMatrix BusinessWorks Plug-in for REST and JSON Software, and "Content-type" response header is not set for Rest and Dispatch activity, users may see the following error in the browser console log:
***************************************************************************************************************************
Signed exchange response without "X-Content-Type-Options: nosniff" header is not supported.
Unsupported version of the content type. Currently content type must be "application/signed-exchange;v=b3". But the response content type was "text/html"
Wrong magic string
Stream ended while reading signed exchange header
***************************************************************************************************************************
This happens because in the google chrome version to 73.x.xxxx.xxx the browser is not able to map the response If your response header is not present in the content type, the browser will not be able to understand how to map the response to the browser console. Due to which you will get the above error.
Environment
Resolution
The issue is only seen on Google Chrome so another workaround is to use some other web browser
Issue/Introduction
Additional Information
Feedback
