tRESTClient has the advanced properties where you can set outgoing headers.
thanks for answering. The problem is that i need to process the HTTP header's Set-Cookie Attribute which is received after i do a SOAP request with login credentials. The proposed solution by Dijke here https://community.talend.com/t5/Design-and-Development/tSOAP-access-the-response-header/m-p/133730#M... is doing that via a low-level Hack through tSystem command line -> calling curl and writing the cookie to a file which i can then process with a file component.
I was just wondering, why i can not access the basic underlying HTTP stuff with the tSOAP component, it would make much sense if a user could generally do that. I know that SOAP is slowly fading away in the API world and REST is the way to go, but there are a lot of "special" APIs out in the wild which have very specific requirements which sometimes are not the standard, so it would be nice to be able to use components like the tSOAP with more options (especially everything which is part of a response).
with best regards,