My Oracle Support Banner

OSB 12c - Custom Headers are not propagated back to the original caller when using the REST binding (Doc ID 2030180.1)

Last updated on MAY 15, 2023

Applies to:

Oracle Service Bus - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Goal

The use case is a proxy service with REST binding, which calls a pipeline that raises a custom fault HTTP 302, and then sets the http:Location header to redirect the caller. However, the http:Location does not work as expected. When using an HTTP binding calling the same pipeline, the redirect does work as expected.

How can one pass back the http:Location header, or any other custom header, back to the caller in a REST binding service?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.