We have a use case with an external SOAP API where we need to 1) use basic auth, 2) support keep-alive/cookies, 3) the cookie is returned in the HTTP header, not the SOAP content from the 3rd party API.
We have to use Soap Method Two due to basic auth; method two does not support keep-alive out of the box. The AO adapter does not return the HTTP headers, so we can't build custom logic to echo the cookie in future requests.
My idea is for the Web Services adapter to echo back the returned HTTP header in a field in the response. For our use case that would allow us to build keep-alive logic ourselves. There are potentially many other use cases where information from the HTTP header might be useful or needed.