723760 - error 500 loading mail.mozilla com/zimbra on fennec nightly 2/2/2012

Status: RESOLVED FIXED

(Infrastructure & Operations :: Infrastructure: Other, task)

Description

[Aakash Desai [:aakashd]]

steps to reproduce:

1. go to https://mail.mozilla.com/zimbra

actual results:
i gt a error 500 page.

expected results:
te login page should load.

note: the login page loads fine on the stocl browser.

Comment 1

[Aakash Desai [:aakashd]]

ping? im still seeing this

Comment 3

[Phong Tran [:phong]]

This sounds like a product issue.

Comment 4

[Dave Miller [:justdave]]

Something appears to have changed in Fennec that causes this.  I can't reproduce this on the 01-28 build, but updating to the 02-08 build definitely causes this.

The server log shows:

nginx.access.log:71.10.136.39 - - [08/Feb/2012:10:51:49 -0800] "GET / HTTP/1.1" 500 1371 "-" "Mozilla/5.0 (Android; Mobile; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1"

nginx.access.log:71.10.136.39 - - [08/Feb/2012:11:01:40 -0800] "GET /zimbra/ HTTP/1.1" 500 1371 "-" "Mozilla/5.0 (Android; Mobile; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1"
nginx.log:2012/02/08 11:01:42 [info] 10722#0: *7712203 client 71.10.136.39 closed keepalive connection

And that's all I can find in the logs, nothing more detailed :|

I can tell you it's definitely something that changed in Fennec that's causing it though.

Comment 5

[Aaron Train [:aaronmt]]

Yea, the user agent.

curl -ILA "Mozilla/5.0 (Android; Mobile; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1" https://mail.mozilla.com
HTTP/1.1 500 For input string: "13.0a1"
Server: nginx
Date: Wed, 08 Feb 2012 19:56:55 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Pragma: no-cache
Content-Language: en-US


curl -ILA "Mozilla/5.0 (Android; Linux armv7l; rv:13.0a1) Gecko/20120208 Firefox/13.0 Fennec/13.0a1" https://mail.mozilla.com
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 08 Feb 2012 19:58:42 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Expires: Thu, 01-Jan-1970 00:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Pragma: no-cache
Content-Language: en-US
Set-Cookie: ZM_TEST=true

Comment 6

[Dave Miller [:justdave]]

Comment 5 places the blame squarely on Zimbra.  I've opened a support case with Zimbra on it.

Comment 7

[Dave Miller [:justdave]]

Now also lives in a Bugzilla bug on their end.

Comment 8

[Robert Kaiser]

Oh, man, a 500 due to browser sniffing, that's pretty bad :(

Comment 9

[Andrew McCreight [:mccr8]]

I'm getting this on Nightly on OSX now, too.  It worked yesterday, Aurora still works.

Comment 10

[Andrew McCreight [:mccr8]]

13.0a1 (2012-02-18) specifically.

Comment 12

[Boris Zbarsky [:bzbarsky]]

Is this bad enough that we should be backing out the UA changes for now?  Will other Zimbra installations be affected too, or is this specific to mail.mozilla.com?  Bug 728610 suggests this is not install-specific.

Alex, I have no way to request tracking on this bug.... :(

Comment 13

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Normally the move the bug to a different component temporarily trick works, but apparently not here :-/

I think this affects all Zimbra installs.

Comment 14

[Dave Miller [:justdave]]

(In reply to Kyle Huey [:khuey] ([e-mail]) from comment #13)
> Normally the move the bug to a different component temporarily trick works,
> but apparently not here :-/

FWIW, your flags are still set, you just can't see/change them.  It'll probably show up in the queries.  You'll have to move it back to the other component to be able to change them though.

> I think this affects all Zimbra installs.

Yes, it does.  See the linked bug on zimbra.com in the See Also field.

Comment 15

[Dão Gottwald [:dao]]

Bug 728797 / bug 572659 fixed this for version 13; 12 and 11 are still affected.

Comment 17

[Alex Keybl [:akeybl]]

(In reply to Dão Gottwald [:dao] from comment #15)
> Bug 728797 / bug 572659 fixed this for version 13; 12 and 11 are still
> affected.

Dao - what are our options for backing out or uplifting a fix for FF11 and 12? On FF11/12, this only affects Native Firefox for Android, correct?

Comment 18

[Dão Gottwald [:dao]]

(In reply to Alex Keybl [:akeybl] from comment #17)
> On FF11/12, this only affects Native Firefox for Android, correct?

yep

Note that the final release versions of Fennec 11 and 12 with these UA strings won't be affected:

Mozilla/5.0 (Android; Mobile; rv:11.0) Gecko/11.0 Firefox/11.0
Mozilla/5.0 (Android; Mobile; rv:12.0) Gecko/12.0 Firefox/12.0

However, if we do chemspill releases, those strings would break zimbra:

Mozilla/5.0 (Android; Mobile; rv:11.0.1) Gecko/11.0.1 Firefox/11.0.1
Mozilla/5.0 (Android; Mobile; rv:12.0.1) Gecko/12.0.1 Firefox/12.0.1

Bug 572659 would strip off ".1" from the rv: and Gecko tokens, so zimbra would work again:

Mozilla/5.0 (Android; Mobile; rv:11.0) Gecko/11.0 Firefox/11.0.1
Mozilla/5.0 (Android; Mobile; rv:12.0) Gecko/12.0 Firefox/12.0.1

Landing this on aurora and beta seems like a viable option to me.

Comment 19

[Dão Gottwald [:dao]]

fixed by bug 572659

Comment 20

[Dave Miller [:justdave]]

For the record, Zimbra appears to have fixed this on their end as well, but it probably won't be in shipping code prior to the 7.2.0 release, which is due in April.