728610 - Zimbra 7.1.3 spits out error 500 if the UA string contains Gecko/13.0a1 or Gecko/13.0.1

Status: VERIFIED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[Cork]

After the UA string change loading the zimbra webmail fails with a 500 error. No posible workaround, the website crashes before loading the login screen.

Tested with Zimbra 7.1.3_GA_3346

Comment 1

[Masatoshi Kimura [:emk]]

Works: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/13 Firefox/13.0a1
Broken: Mozilla/5.0 (Windows NT 6.1; WOW64) Gecko/13.0a1 Firefox/13.0a1
Works: Mozilla/5.0 (Windows NT 6.1; WOW64) Gecko/13 Firefox/13.0a1

Comment 3

[Boris Zbarsky [:bzbarsky]]

I'm going to reopen this so we can actually track this for 13.  We may need to back out the UA change.  :(

Comment 4

[Andrew McCreight [:mccr8]]

I don't know if this is related, but my Google search page looks weird now.  No ads, no side bar, it doesn't display the weather if I search for "mountain view weather", etc.

Comment 5

[Andrew McCreight [:mccr8]]

(eg it feels like the google search result page is falling back to a very primitive form because it can't understand the UA string or something)

Comment 6

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

That's bug 651674.

Comment 7

[Boris Zbarsky [:bzbarsky]]

Please don't move this out of Core, because the tracking flag will get lost.  Think of this as the "back out the UA change" bug if you want.

Feel free to file a separate evang bug if you think we need one, but note that we have one for Zimbra already (for mail.mozilla.com).

Comment 8

[Boris Zbarsky [:bzbarsky]]

Oh, interesting.  Tracking flag is still there, even though this is in evang?  Leaving it here, then.

Comment 9

[Henri Sivonen (:hsivonen)]

Based on comment 1, we could just drop the "a1" part from the UA string to align Nightly and Aurora better with release for sniffing behavior.

FWIW, when I tested various UA string proposals, I thought that Gecko/12.0 was OK, because I tested Zimbra without "a1". I did notice that Zimbra gives error 500 if the character after "Gecko/" is not a digit.

Comment 10

[Masatoshi Kimura [:emk]]

Now http://demo3.zimbra.com/ works for me. Is there any other Web pages to test the breakage?

Comment 11

[Dão Gottwald [:dao]]

(In reply to Masatoshi Kimura [:emk] from comment #10)
> Now http://demo3.zimbra.com/ works for me. Is there any other Web pages to
> test the breakage?

https://mail.mozilla.com/

Comment 12

[Masatoshi Kimura [:emk]]

Thank you.

Comment 13

[Matěj Cepl]

Just +1 from me ... http://demo3.zimbra.com/ is broken as well as our internal Zimbra web user interface (which is Zimbra 7.1.2_GA_3268 (build 20110804120319)).

Comment 14

[Matěj Cepl]

(In reply to Matej Cepl from comment #13)
> Just +1 from me ... http://demo3.zimbra.com/ is broken as well as our
> internal Zimbra web user interface (which is Zimbra 7.1.2_GA_3268 (build
> 20110804120319)).

and yes with US

Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1

both websites work for me again.

Comment 15

[Gervase Markham [:gerv]]

Matej: are you sure? That looks like the UA that everyone says is breaking things. Just to be crystal clear, can you post a broken UA and a working UA?

Gerv

Comment 16

[Matěj Cepl]

(In reply to Gervase Markham [:gerv] from comment #15)
> Matej: are you sure? That looks like the UA that everyone says is breaking
> things. Just to be crystal clear, can you post a broken UA and a working UA?

No, it isn't the same.

The difference is

Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1
Mozilla/5.0 (X11; Linux x86_64; rv:13) Gecko/13.0a1 Firefox/13.0a1

Comment 17

[Matěj Cepl]

(In reply to Gervase Markham [:gerv] from comment #15)
> Matej: are you sure? That looks like the UA that everyone says is breaking
> things. Just to be crystal clear, can you post a broken UA and a working UA?

Yes, there was a typo in comment 14, that was the original unchanged UA. With the changes indicated in comment 16 it really works.

Comment 18

[Gervase Markham [:gerv]]

Matej: I'm still not clear, sorry. The two UAs you give differ in the rv: token; I thought the breakage was because we changed the Gecko token?

Please fill in this form:

Broken: <insert UA here>
Working: <insert UA here>

:-)

Gerv

Comment 19

[Cork]

For me its:
Broken:
Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/13.0a1 Firefox/13.0a1
Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/13.0a1 Firefox/13.0a1
Mozilla/5.0 (X11; Linux x86_64; rv:13) Gecko/13.0a1 Firefox/13.0a1

Works:
Mozilla/5.0 (X11; Linux x86_64; rv:13) Gecko/20100101 Firefox/13.0a1
Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/20100101 Firefox/13.0a1
Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/13.0 Firefox/13.0a1

So ya its definitely the Gecko/ that affects the server.

Comment 20

[Gervase Markham [:gerv]]

Awesome. Then we are on the right track with our fix.

Gerv

Comment 21

[Daniel C]

I can confirm that the respun nightly (20120220074932, which contains the fix from bug 572659) fixes this issue. Both http://demo3.zimbra.com/ and https://mail.mozilla.com/ gave 500 errors in the first nightly but show login pages in this build.

Comment 22

[Matěj Cepl]

Thank you, today's nightly works correctly for me as well with our company Zimbra.

Comment 23

[Alex Keybl [:akeybl]]

We're using bug 588909 to track the backout and steps forward. FF13 should no longer be affected now that the backout has been performed.