Closed Bug 751486 Opened 13 years ago Closed 13 years ago

Don't expose the Gecko patch level (XX.Y [ex. 15.0]) in the UA string, only show the major version (XX [15])

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Version:
15 Branch
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: Virtual, Unassigned)

Details

(Keywords: nightly-community)

Drop ".0", because it's useless now as we don't expose alpha, beta and RC stages (bug #728797) and we also don't expose patch level (bug #572659)
This can in one go fix both Gecko info in UA string: rv:XX.Y [ex. rv:15.0] => rv:XX [ex. rv:15] Gecko/XX.Y [ex. Gecko/15.0] => rv:XX [ex. rv:15] Is: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:15.0) Gecko/15.0 Firefox/15.0a1 Will be: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:15) Gecko/15 Firefox/15.0a1
The second number isn't "patch level", it's reserved for major updates (e.g. 3.0, 3.5, 3.6).
No longer blocks: 572659
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
tracking-firefox15: ? → ---
Resolution: --- → INVALID
If we will use it, that's fine. It can stay. But after Firefox 4, I didn't see that major update info was used even once. Didn't it become useless now in main Gecko line ? or we simply keeping it for ESR sake ?
It doesn't really matter whether we use it. UA string parsers correctly take it into account and will break if we remove the dot.
It matters. Now, as we replacing Gecko/<date> with Gecko/<version> (bug #588909), this change shouldn't break anything more. At least changing Gecko/XX.Y [ex. Gecko/15.0] => rv:XX [ex. rv:15] will be unnoticeable. Don't you think ? Isn't it the best time to deal with it ? :)
We can't remove if from the Firefox token nor the rv token, so there's no point in removing it from the Gecko token. This would only encourage people to sniff for Firefox rather than Gecko, thinking the former had more accurate version information.
OK, that's explains a lot!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.