Closed Bug 1230783 Opened 9 years ago Closed 8 years ago

chase.com thinks latest stable Firefox is out of date if any additional tokens in User-Agent

Categories

(Web Compatibility :: Site Reports, enhancement)

Firefox 42
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: josh, Unassigned)

References

Details

(Whiteboard: [needstriage])

Attempting to log onto a Chase banking account using the latest stable Firefox (42) produces a message about using an out-of-date browser, and pointing to the download pages for several browsers, including Firefox.

By switching my user-agent, I've confirmed that they seem to check the Gecko date, and they break with current versions of Firefox that use the static "Gecko/20100101" string (as changed in bug 591537).  Changing it to "Gecko/20151205" allowed logging in.

This need fixing on Chase's end.
Correction (fixing the title and importance): turns out they don't seem to pay attention to the Gecko date after all; the user-agent switcher I used had some UI quirks that made it not do what I thought it did.  After more careful checking, it appears that Chase rejects the Firefox 42 user agent if it has any other tokens appended after the "Firefox/42.0" at the end, such as done by browsers based on Firefox.  This is still a bug on Chase's side, but not the same bug, and not as serious.
Severity: major → enhancement
Summary: chase.com uses Gecko date for version check, thinks latest stable Firefox is out of date → chase.com thinks latest stable Firefox is out of date
Summary: chase.com thinks latest stable Firefox is out of date → chase.com thinks latest stable Firefox is out of date if any additional tokens in User-Agent
See Also: → 1277111
Hi Josh. Do you still notice this issue with Chase? Or was this limited to version 42?
Flags: needinfo?(josh)
Whiteboard: [needstriage]
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(josh)
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.