Hi Alec, Having considered this issue my suggestion is to use a custom transformer which invokes the external content provider with values from the pipeline document and sets the user agent header from the orginal request. The response from the external request is then aggregated or replaces the document in the pipeline.
I developed such a custom transformer for testing and using SOAP services. In such a scenario the transformer has to set the outgoing HTTP request with the value of the desired SOAP action instead of the user agent. I will post the code asap although I have an idea that I put it on this list some 4 years ago. Hope this helps, Warrell
