This content has been marked as final. Show 8 replies
there currently is no provision to allow users to add their own HTTP headers.
You may want to file an enhancement request for that.
Thank you so much for your reply, Maurice.
I believe it would be a good feature, will surely file for an enhancement with Oracle.
Hi, all1 person found this helpful
I remembered we did similar enhancement for SALT. I will confirm with CCE team and post the related bug number and patch to you.
It has been enhanced on salt11gR1 and addressed in edocs as below:
Thank you so much for pointing us in the right direction.
Sincerely appreciate your replies.
We are using the following:
TUXEDO10gR3 PATCH LEV=44
SALT Patch Lev = 15
For obvious reasons, it would be difficult (almost impossible) for us to move to 11gR1 immediately.
It would be wonderful if we can get a patch for 10gR3.
Please do let us know about the patch for 10gR3 if it exists.
Thanks a lot again.
just to be clear: do you need to add HTTP headers or SOAP headers? The title of this thread implies the former.
The documentation Xu points to is for adding SOAP headers, which is indeed available but since 11gR1.
If what you need is custom HTTP headers that is not implemented yet.
Thanks for confirming this.
It clarifies the doubts that I was having while reading through the documentation Xu pointed to.
Yes, we need to add HTTP Headers (not SOAP header).
For now we just need to add Basic Authentication HTTP Header for outbound service calls.
We have developed a plugin to do that for now.
And even if the salt plugin takes care of adding the Basic Authentication in the HTTP Header for outgoing calls, I guess we do not have any option to include some custom information in the HTTP Header which might be required in the future.
At-least, not unless we request that enhancement.
Bringing the plugin into our mix requires a lot of changes to our architecture including inclusion of AUTHSVR in the UBB,
Which, in turn, makes it imperative to change the endpoint clients of our application.
In addition to that, the incoming web service calls also need to include TUXEDO authentication information, which would again require either communicating the authentication information to the consumers of our service or device some kind of a proxy which would add the authentication information for all the incoming requests!
With these facts in mind, we were wondering if we have an easier way to include the HTTP header information.
As you say, Maurice, it seems it is not possible yet.
Thank you again for your replies.