Closed Bug 651339 Opened 13 years ago Closed 13 years ago

Firefox 4.0 and 4.0.1 send incorrect build date in HTTP User-Agent header

Categories

(Firefox :: General, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 592342

People

(Reporter: jdMorgan56, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

The date in the HTTP User-Agent header sent by both Firefox/4.0 and 4.0.1 indicates 01-January-2010.  As it's now 2011, an update is likely in order.

The date in the recent Firefox/3.6.16 UA string is OK, as far as I can tell (from a webmaster/Firefox user's vantage point).



Reproducible: Always

Steps to Reproduce:
1. Examine Firefox/4.0 or /4.0.1 User-Agent headers logged by any web server, or use something like the "Live HTTP HEaders" add-on to view outgoing HTTP request headers.
2. Note date in HTTP User-Agent header indicates 2010.
3. Note that this seems to be OS-independent.
Actual Results:  
Webserver log samples:
"Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0"
"Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0"
"Mozilla/5.0 (Windows NT 6.0; rv:2.0) Gecko/20100101 Firefox/4.0"
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0"
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1"

Expected Results:  
Expected to see a date after February 2011 in Firefox/4.x User-Agent strings.

Send correct build date in HTTP User-Agent header.
Build date was intentionally frozen (bug 591537).
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Resolution: INVALID → DUPLICATE
You need to log in before you can comment on or make changes to this bug.