We get more and more traffic for FileAPI v2 and looking for an option how to monitor traffic from connectors for quick reaction to errors. The simplest and convenient for all solution to use "User-Agent" header field. The current sdk already has client_lib_id (introduce in #15) but it was added for another reason (indicate link between particular uploaded file and client lib version).
DoD:
SDK adds client_lib_id and version as "User-Agent" for all http requests (doesn't mater GET\POST\DELETE)
If you want to keep the original "User-Agent" too, then add information in the begging of "User-Agent" . An example:
original user-agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022)
new user-agent: smartling-api-sdk-java/2.0.2 Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022)
User-agent string has format {client_lib_id}/{version}
We get more and more traffic for FileAPI v2 and looking for an option how to monitor traffic from connectors for quick reaction to errors. The simplest and convenient for all solution to use "User-Agent" header field. The current sdk already has
client_lib_id(introduce in #15) but it was added for another reason (indicate link between particular uploaded file and client lib version).DoD:
client_lib_idand version as "User-Agent" for all http requests (doesn't mater GET\POST\DELETE)Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022)smartling-api-sdk-java/2.0.2 Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.21022){client_lib_id}/{version}