SDK version required for User-Agent changes in 11.36
Tuesday, July 28, 2020 at 01:47pmHello, we were informed that a change will be coming to the API interactions in the 11.36 version. If we integrate using the Java SDK, is it necessary to upgrade to the latest version of the SDK in order to correctly handle the removed user-agent header?
- Removed "user-agent" from callbacks: As anticipated in the Customer Notice of 11.35's Release Notes, the "user-agent" header has been removed from callbacks.
Thanks! Kevin
Reply to: SDK version required for User-Agent changes in 11.36
Tuesday, July 28, 2020 at 02:06pmHi Kevin,
Because 11.36 hasn't been deployed to any public accessible environment, below is my own understanding to this product change. But in general, this change ONLY affects the callbacks OSS sends to your listener, and WON'T affect normal API calls.
A callback request today looks like:
POST {your_callback_url}
Request Headers:
content-type : application/json; charset=utf-8
authorization : Basic {your_callback_key}
content-length : 229
host : {your_site_host}
user-agent :
accept-encoding : gzip,deflate
Request Body:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_CREATE","sessionUser":"18EZDL44xgsX","packageId":"cn9hB8JABiuQg4FPcUUsbrwgFNs=","message":null,"documentId":null,"createdDate":"2018-08-29T14:29:01.183Z"}
Where in the request header, "user-agent" is with value of an empty string. And after 11.36, this attribute will be removed from the request headers since it won't make a whole lot sense if value is left empty.
Duo
Reply to: SDK version required for User-Agent changes in 11.36
Tuesday, July 28, 2020 at 02:13pmThanks, Duo! We'll take a look at our code specific to the callbacks and maybe check our firewall settings too. Thanks again!