E9.2 change user-agent when run a orchestration to consume external rest-api

[arrozpegao]

hi,
i found a problem with user-agent tag. It's sent with rest-api call, and it´s stopped by a firewall due version number inside user-agent tag (Chrome/39.0.2171.95)
can i customize user-agent value in any way?

Thanks in advance.

 

[DaveWagoner]

I think I asked for allowance to fully customize external rest calls for reasons similar to this, but it was not entertained as an option. I'll look for my request if I get a few mins.

A possible workaround would be to use a low cost 3rd party webhook service or API proxy/gateway to handle the final call to the blocking client, where you DO get to change headers and pass-thru the payload.

 

[arrozpegao]

i answer my self, just adding user-agent value in HEADER in the connector.
it's enough
ex: user-agent: JDE