+++ This bug was initially created as a clone of Bug #728831 +++ Steps to reproduce: 1) Load http://www.delorie.com:81/some/url.txt Actual results: The User-Agent header exposes the security patch level as either a minor version number or as an alpha/beta/pre indicator. This data is exposed twice: in the Gecko version and in the application version. While it is of value to expose this data to e.g. AMO, exposing it to all sites makes the browser more fingerprintable (see https://panopticlick.eff.org/ ) and doesn't serve a purpose more important than user privacy. Point releases don't change functionality beyond security and stability fixes, so sites shouldn't be sniffing the patch level anyway. Making trunk, alpha and beta builds look like release builds for sniffing purposes reduces sniffing-related failures that waste time when treated as functionality-related regressions by mistake. Expected results: Expected the version numbers to show the major version of the most recent Firefox beta that Mozilla has shipped and not to show the security patch level or an alpha/beta/pre indicator. Additional information: Internet Explorer doesn't expose the security patch level in its UA string.

> Point releases don't change functionality beyond security and stability fixes, > so sites shouldn't be sniffing the patch level anyway. This is wishful thinking. Point releases fix serious bugs. Do you really need examples?

Sorry, I assume my previous comment was nonsense

The current patch in bug 728831 would fix this.

If this is not being done in desktop or mobile, doesn't need to block basecamp