Is it a good idea to custom User-Agent of request header ?

[zhatongning]

export function defaultHeaders(
  sdkKey: string,
  info: IInfo
): Headers {
  const {userAgentBase, version} = info.sdkData();

  const headers: Headers = {
    'Content-Type': 'application/json',
    'User-Agent': `${ userAgentBase ?? info.appType }/${ version }`,
    'Authorization': sdkKey
  };

  return headers;
}

Here is the implement of the defaultHeaders function.The field 'User-Agent' comes from the userAgentBase which is "Browser-Client-SDK" in most time concat the version.I met a question in Dingtalk H5 in which the fetch to server will fail because the customed User-Agent cause DingTalk agent throwing away the request body. May Dingtalk doesn't handle it friendly, and I also don't think it is good idea to customize User-Agent filed like this.

The "User-Agent" header field contains information about the user agent originating the request, which is often used by servers to help identify the scope of reported interoperability problems, to work around or tailor responses to avoid particular user agent
limitations, and for analytics regarding browser or operating system use.

it's from rfc. The customized User-Agent isn't consistent with the purpose " analytics regarding browser or operating system use"