523554 - Accept-Language header not sent at first start with new profile

Status: NEW

(SeaMonkey :: General, defect)

Description

[Thomas Bertels]

SeaMonkey 2.0rc2 and 2.0.1pre don't send Accept-language header.
The trunk version does, but I think the final 2.0 version should too.

Open the URL to reproduce.

Comment 1

[Tobias Fischer]

Hmm, using the todays SM 2.0.1-Nightly-Build seems to send the Accept-Language Header (Copy & paste output from URI above):

GET /ip/headers HTTP/1.1
Host: www.ioerror.us
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091021 Mnenhy/0.7.5.20005.h5 SeaMonkey/2.0.1pre
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,de-de;q=0.7,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive

Comment 2

[lenochod]

I using SeaMonkey 2.0RC2 and OK for me.

GET /ip/headers HTTP/1.1
Host: www.ioerror.us
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: cs,en-us;q=0.7,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: windows-1250,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive

Please try in Safe mode ( http://kb.mozillazine.org/Talk:Safe_Mode#Safe_Mode_in_SeaMonkey_2 ), or with a new profile ( http://kb.mozillazine.org/Profile_Manager#Creating_a_new_profile ).

Comment 3

[Robert Kaiser]

Canceling blocking request as nobody can confirm this for now, it also works for me with current 2.0.1pre code.

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5pre) Gecko/20091021 Lightning/1.0pre SeaMonkey/2.0.1pre
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: de-at,de;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: UTF-8,*

Comment 4

[Thomas Bertels]

Actually, I *was* using a new profile.
It looks like it can only be reproduced with a new profile. Can you confirm that ?

Comment 5

[Thomas Bertels]

After looking at your headers, and trying it out, I found out that we have to modify the language settings to enable the Accept-language header sending (you all did).

Comment 6

[Tobias Fischer]

While using a clean Test-Profile I can confirm this issue:

GET /ip/headers HTTP/1.1
Host: www.ioerror.us
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091021 SeaMonkey/2.0.1pre
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate
Keep-Alive: 300
Connection: keep-alive

Than modify the Language-Settings (just move en-US down under en, than back) and the Accept-Language Header was now sent:
Accept-Language: en-us,en;q=0.5

Have also tested with an SMrc2 20091017 de l10n-Build, and out of the box it will not send the Accept-Language-Header too. Hmm.

Comment 7

[lenochod]

It's repeated in the first launch of a new profile.

After the restart the browser everything is OK.

Comment 8

[Serge Gautherie (:sgautherie)]

Can you reproduce with Firefox v3.5.3 / v3.6a1 / current v3.7a1pre?

Comment 9

[Thomas Bertels]

(In reply to comment #8)
> Can you reproduce with Firefox v3.5.3 / v3.6a1 / current v3.7a1pre?

No, I couldn't reproduce with Firefox v3.5.3.

I wonder if Version should really be set to Trunk because this bug can't be reproduced with the trunk.

Comment 10

[Robert Kaiser]

(In reply to comment #9)
> No, I couldn't reproduce with Firefox v3.5.3.

You tried a new profile as well there, right?

> I wonder if Version should really be set to Trunk because this bug can't be
> reproduced with the trunk.

I don't see any notes in here that 2.1a1pre wouldn't show that behavior. That said, we don't have a version entry for SeaMonkey 2.0 Branch yet, need to file a bug to get it added.

I wonder if the preference has been moved somewhere else than it was before and ends up not being defined in a new profile because of that.

Comment 11

[Thomas Bertels]

(In reply to comment #10)
> (In reply to comment #9)
> > No, I couldn't reproduce with Firefox v3.5.3.
> 
> You tried a new profile as well there, right?

Yes, I did.

> > I wonder if Version should really be set to Trunk because this bug can't be
> > reproduced with the trunk.
> 
> I don't see any notes in here that 2.1a1pre wouldn't show that behavior.

It's in the the first comment (I didn't mention "2.1a1pre", but...).