OSB 126.96.36.199 Sends Content-Type: Text/plain In REST Http GET Outbound Call when sending an an Empty Content-Type
(Doc ID 2682446.1)
Last updated on OCTOBER 21, 2021
Applies to:Oracle Service Bus - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, OSB Transports
OSB 220.127.116.11 sends Content-Type: text/plain in REST http GET outbound call
The use case is OSB used as a proxy in between client and service provider communication.
A client sends http GET request together with Content-Type: application/json and service provider expects empty Content-Type or Content-Type: application/json otherwise it fails.
This worked fine without OSB and with OSB 11g.
After upgrade to OSB 18.104.22.168 request http GET with Content-Type: application/json fails because OSB JSON parser tries to parse empty payload.
This issue has been fixed by patch 27996858 "REST GET Operation with Content type and No Payload Leads to Exception".
The patch removes Content-Type from request so it is not visible in OSB pipeline. Therefore OSB pipeline can not set client Content-Type as a work around.
The issue is that even there is no Content-Type OSB sends default Content-Type: text/plain to service provider which then fails.
to be able to receive an empty content-type when an empty one is sent
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document