Closed Bug 373965 Opened 19 years ago Closed 19 years ago

Cannot enter my webmail.

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: steveboy, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2 Build Identifier: Camino Version 2007022813 (1.0.4Int) The version 1.0.4 works, but the same 1.0.4 multilanguage version wich I use is not supported, even if 1.0.+ versions are listed in the supported browsers list. Firefox is fine too. Reproducible: Always Steps to Reproduce: 1.Use Camino 1.0.4 multilanguage. 2.Try to open reported URL. 3.Browser is not supported. Expected Results: Should work without a problem.
This is a bug in the host's browser-detection; they're getting confused by the "(MultiLang)" in the user-agent string of the ML build. I can't find the script that does it exactly, but from the output, it looks like the script is confused by two sets of strings in parentheses. You should inform the site admins that their detection is broken for all browsers which add pieces of the user-agent string in parentheses (which is a common practice for Firefox on Linux distributions and many Firefox extensions, in addition to Camino ML).
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
If this is so widely broken, perhaps it's worth kicking to TE if the site doesn't respond in a timely manner.
(In reply to comment #1) > This is a bug in the host's browser-detection; they're getting confused by the > "(MultiLang)" in the user-agent string of the ML build. > > I can't find the script that does it exactly, but from the output, it looks > like the script is confused by two sets of strings in parentheses. > > You should inform the site admins that their detection is broken for all > browsers which add pieces of the user-agent string in parentheses (which is a > common practice for Firefox on Linux distributions and many Firefox extensions, > in addition to Camino ML). > I wrote to the support, they just came back on me with a simple "Camino is not supported by Webmail" answer, "we recommend that you use firefox". As it is supported, just not the multi version due to the double exclamation marks, it is perhaps necessary that this is fixet at the UserAgent level in Camino. Thanks for your fast and great support. Greetz Steve
(In reply to comment #3) Since they support Firefox, there are NO reason they should not support Camino as well. Since both browsers use the same Gecko rendering engine. Point them towards www.geckoisgecko.org and tell them to fix their browser-detection code.
If comment 1 is accurate -- and I trust Smokey -- then they only support Firefox on Windows. That is probably worth calling to their attention, and as I said, if they don't respond positively, let's kick this to TE.
No, their "we don't support you" page (that you see if you visit with an ML version of Camino) claims they support Fx 1.0 and above on all platforms, and Camino 1.0 and above on Mac OS X. It also spits out what they think your user-agent is, divided among various parts, and this result is all confused, showing it's their parsing bug. https://webmail.vo.lu/BrowserCompatibility.aspx Please point them to their own page, and tell them to check again with a Gecko browser with user_pref("general.useragent.extra.some_extra", "(some_extra)"); (as used by Camino ML, certain Firefox extensions, and Firefox as distributed by many Linux distros, e.g."Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy)")
I'll forward all your infos to them, but they don't seem very responsive as their only mail showed already. I should reach their admin directly, but I get in touch with their support only for the moment! I'll come back to tell what they they did about their problem. Excuse me, but what does "let's kick tis to the TE" mean? Greetz
"TE" is Tech Evangelism; i.e., if you don't get positive results, we'll put official Mozilla pressure on them to fix their broken code, since their brokenness is affecting the ability of a large number of Mozilla-based browsers to access the site.
You need to log in before you can comment on or make changes to this bug.