Hi Greg > I agree with what you are saying about replacing the UA being the "right > thing" for most use cases. In this case, the app to which I'm forwarding > my requests has some conditional logic based on the UA in the request so > I do need to pass it through. Ok.. I think this is quite valid.. so maybe a enhancement request would be good so that we can implement a feature to turn off replacing UA > I tried just setting a transport header > but I'm not having any results. I'll keep trying and see what I can do. > Ok.. if you've tried this, there is no way to get it to work with the stock code unless you patch it.. > Failing that, is there any place in the process where I can inject some > custom code _after_ the transport headers have been set for the outgoing > request? Maybe in a Formatter? > No, this is because its set as a transport level parameter when the transports are initialized. If you are willing to create or use a patched version, it would be a simple fix however.
cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com
