WLS 18.104.22.168: WebLogic Workshop service control changing Httpheader while accesing Webservice.
(Doc ID 1235024.1)
Last updated on MARCH 09, 2019
Applies to:Oracle Workshop for Weblogic - Version 9.1 and later
Information in this document applies to any platform.
At a high level, a handler in WebLogic is changing the HTTP header information. Even if the HTTP header is customized to include the SOAPAction element, it is being modified by WebLogic in the call flow thus causing the issue of the end request not having the SOAPAction element in the HTTP header.
The control calls an external Webservice.
When a client handler is used with a clientgen generated client then the header is added without any problems and received successfully at the service end.
But when a service control is used and configured using the same handler, then the web service container seems to neglect the added headers.
So, its clear that you can use client handlers to add the header, but client handlers do not work with service control.
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