191311 - web site can't identify mozilla support for cookies

Status: RESOLVED EXPIRED

(Core :: Networking: Cookies, defect)

Description

[Philip Birk-Jensen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212

(the site is on danish) When I try to login to the site, it sayes that my
browser do not support cookies, and I should turn this feature on before
proceeding. When I try on Internet Explorer, it dosn't complain.

Reproducible: Always

Steps to Reproduce:
1. Entering http://heroes.jubii.dk/, and hitting enter
2. Writing my user and my password, and hitting enter
3. Here I get the error message from http://heroes.jubii.dk

Actual Results:  
A text was displayed, telling me how to add cookies (in MSIE), and that I
couldn't login without cookie support.

Expected Results:  
Made it compatible

I have MSIE 6 installed as well

Comment 1

[R.K.Aa.]

What are your settings for cookies in preferencs?

Comment 2

[R.K.Aa.]

Never ind that question.. confirming the issue. I registered and tried to log in
with same result as reporter. Setting is to allow all cookies. Smells like evang.

Comment 3

[Zook Valem]

Or perhap a bad web scripting....

Comment 4

[Ruslan Ismailov]

Well, this cire definitly have bad scripting for object WFM. But seems that
cookies support check's into some asp - server side code.

Comment 5

[Chuck Mattsen]

Am having the same problem with build 2003032308 (but only began to occur
somewhere in the past couple of nightly builds, first noticed this a.m. on sites
that previously worked with no problem).  I.e., http://www.usbank.com, click on
Internet Banking.  Even with "accept all cookies" setting, message returned is
the "You must have cookies enabled...blah, blah, blah" so cookie support seems
somewho broken in the most recent build(s).

Comment 6

[Sam Hulick]

I have build 2003032408.  The cause of this cookie problem on recent builds is
the "Disable cookies for Mail and News" option.  Unfortunately, if that option
is turned on, it also randomly disables cookies for web sites as well.

Comment 7

[Sam Hulick]

Looks like this is fixed in 2003032508

Comment 8

[Sam Hulick]

I take that back.. still broken in 2003032508.

Comment 9

[[e-mail]]

the "disable cookies for mailnews" bug was fixed yesterday - try using today's
trunk.

i'll investigate the original report, and try rolling a cookie log to see what's
up. thanks for confirming, RK.

Comment 10

[[e-mail]]

reporter: i'm unable to verify because the site is behaving strangely for me
(timeouts, incomplete data etc). could you (or RKAa) please generate a cookie
log for the site?

instructions for win32 can be found at
http://bugzilla.mozilla.org/show_bug.cgi?id=193951#c1.

Comment 11

[Philip Birk-Jensen]

It dosn't write anything in the error log, even though I tried 3 times
(completing the steps in the instruction everytime). Sometimes the server is
under a heavy load, this could cause the timeouts.

(another question, not in connection with this bug - How do I change build?)

Comment 12

[Ruslan Ismailov]

Attachment: Cookies log

Hm... I don't see any reject's. BTW, I use 1.4

Comment 13

[[e-mail]]

Ruslan: you do see the site complain about cookies being disabled though, right?

Doesn't look like the log is going to help much here... I'll see if I can look
into it more.

Comment 14

[Jan Tore Ynnesdal]

I can confirm this on the latest build. 

I use the ASP/VBSCript object MSWC.BrowserType to detect if cookies are
supported, and in both Mozilla and Firebird i get the same result. Simple ASP
script for checking this:

Set browsercheck = Server.CreateObject("MSWC.BrowserType")
cookiesupport = browsercheck.cookies
Response.Write cookiesupport

This says "false" when I run it.

I also have all cookies turned on, and it works in IE/Opera - and it worked
nicely before.

Comment 15

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 16

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.