Java client tools should set a custom user agent string
Related to https://redmine.dataone.org/issues/7047
It looks like nowhere in
d1_libclient_java do we set a user agent string. Aside from being best practice, it limits our ability to customize our infrastructure around it. For example, OPC is running into HTTP 413s due to overrunning their TLS renegotiation buffer and we can't effectively whitelist their requests, which come from our Java client tools, to allow them to upload large files.
#1 Updated by Bryce Mecum over 1 year ago
From Chris via Slack: It looks like d1_libclient_java does set a UA string of "Apache-HttpClient/4.3.6 (java 1.5)" but my guess is that the UA string is the same for the client tools when initiated from the CN to an MN as from a user to an CN/MN so we really need different ua strings.