Most "browsers" such as Chrome or Safari will always include this however often with libraries or command line tools which are typically used via bad actors do not set this as standard so the browser fingerprint changes.

I now recommend combining the following headers into a MD5 HASH which creates a unique fingerprint which does not inconvience the user:

(the fact that MD5 is not considered secure anymore is not relevant in this scenario)

Accept, Accept-Encoding, Accept-Language, Connection, User-Agent, Sec-Fetch-Dest, Sec-Fetch-Mode, Sec-Fetch-Site, Sec-Fetch-User, Upgrade-Insecure-Requests, sec-ch-ua, sec-ch-ua-mobile, and sec-ch-ua-platform.