How does OSB processes HTTP Error Response Codes Different From 200 (Doc ID 3034175.1)

Last updated on JULY 15, 2024

Applies to:

Goal

Customer has detected that, for some native REST services (Business Services), when the http response code is other than 200 (let's say 304), statistics in EM console are showing request result as an error. In their opinion, 304 is not a HTTP code which represents an error and this error should not be reflected in statistics.

This fact, considering http-response-code 304 as an error, means that within the pipeline service, the response is also considered an error and flow goes into error handler, and it should not do that. In this case the workaround is verify the response code within the Error Handler and in case a 304 is detected, a "Reply with Success" action is risen to avoid the error to be reflected in PS-PP statistics. This way business service behavior and BS statistics are being affected.

Why OSB is considering this http-response-code 304 and all others that are not 200 as errors?
 

Solution

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