Whenever I install a new nightly build on Linux, Slashdot responds in a strange manner. The very first time I start up Mozilla from the latest install, it acts like I'm not logged into Slashdot (when, in fact, I am). If I exit from Mozilla and start up again, everything is fine. However, if instead of exiting from Mozilla, I try to login to Slashdot, Sladhot returns me to index.pl like I succeeded, but I still get the default page rather than my customized page, like the Slashdot cookie wasn't geting set. I've seen this behavior for a while, and it's still there with build 2000071308.
The bug description is too abstract. Please give a more detailed sequence of steps for reproducing the problem.
Steps to reproduce: 1) Get an account on Slashdot. 2) Using Mozilla, log into that Slashdot account. 3) Customize the account's frontpage options to the point where it's the front page while logged in is obviously different from th front page while logged out. 4) Exit from Mozilla. 5) Download and install a new Mozilla nightly build. 6) Start up the just installed Mozilla and vist Slashdot. The front page will be like you aren't logged in, although you have a slashdot cookie that has your login information. Now, you can either: 1) Exit Mozilla, restart it, and visit Slashdot again. Now everything will be fine. or 2) Enter your username and password into the approriate text fields and click on the "login" button. You'll be returned to the Slashdot front page, but it will still look like you aren't logged in.
Alright, I've simplified the test case a little. The new steps are: 4) Exit from Mozilla. 5) Delete the file component.reg, wherever it might be. 6) Start up Mozilla and visit Slashdot. The front page will be like you aren't logged in, although you have a Slashdot cookie. that has your login information.
Unable to reproduce using win32. Of course the sequence of steps is still not detailed enough -- in particular I have no idea how to "customize the account's front page." But it is recognizable when I'm logged in as it says: This page was generated by a Group of Random Geese for <username> I created the account using 4.x. I ran mozilla, went to the page and logged in. The above message was displayed. I closed the browser, deleted the two copies of component.reg (one in bin and one in bin/psm) and restarted. Went back to the page. Without any explicity login I saw the above message indicating the I was logged in. Could this be a linux-only problem? Have you tested using win32 to see if you can reproduce the problem there?
Right, the "This page was generated by <sillyness> for <username>" is enough to show that you're logged in. I will attempt to reproduce with Win32.
Unable to reproduce on Win32 with the latest build. Looks like a Linux only problem. Also, as an addition to the recipe, Slashdot should be the homepage while testing, and the browser should start up on the homepage.
Summary: Weird cookie behavior with Slashdot → Weird cookie behavior with Slashdot (linux only)
Take a look at 40449. These two bugs sure seem to be related.
Also take a look at bug 46514.
I've also noticed this with the Linux nightlies, most recently 2000072408. When I get a new build, I generally set Slashdot to be my home page. I have to log in *twice* before my logged in page comes up. This is my method of reproducing this bug: (Assuming you have an account on Slashdot, and a new build) 1) Set your homepage to Slashdot. Exit mozilla. 2) Start up mozilla, log in. (Doesn't seem to matter whether you store the form details or not). 3) Page which is shown is non-logged in page. 4) Log in again. 5) This time you get the logged in page.
I also notice the problem with having to log in twice on Win32 machines, too.
Although I haven't investigated this particular case, it is probably another example of a cache problem (similar to 46514) rather than a cookie problem. Reassigning to Neeti. If I'm wrong, then assign it back to me and I'll investigate further.
Assignee: morse → neeti
Status: ASSIGNED → NEW
Component: Cookies → Networking: Cache
Note: If your cookies aren't set already, you need to log in *twice* whether you are using Mozilla, Netscape, or IE.... all platforms, too! It would appear that something is flawed with the login / cookie setting on Slashdot. I believe it started happening a couple of months ago when Slashdot switched servers, and it hasn't been corrected since. Because the default action is to save the cookie, it just was probably overlooked.
Based on wdormann's last comment, I would conclude that this is certainly a server problem and not a browser one. Especially if it is happening on netscape 4.x and on IE as well. So we probably should close this out as invalid but I'll leave that to neeti to decide. In any case, it no longer seems to be a cache problem. An obvious suggestion is for someone to notify the site. But from past experience, I have found that to be an excercise in futility.
This (might) be two seperate problems: having to log in twice, and not being logged in at all if you start up Mozilla with no component.reg file. Unless the two problems are basically the same, I don't think that this bug should be closed.
Summary: Weird cookie behavior with Slashdot (linux only) → Cookie service created AFTER 1st HTTP request if component.reg missing (linux only)
I've just noticed that the 'double login' problem occurs with NS4 as well. I agree with Morse that it's a server problem, and therefore this part of the bug is invalid.
This bug has been morphed and is now difficult for people to understand (there's a lot of non-relevant comments that they have to read through). I suggest that the original summary line be restored (referring to the double login) and this bug then be closed out as invalid because it is a server issue. Then a fresh bug be opened on the new symptoms as you have described them along with your understanding of why it is happening. Also, you seem to have a very good grasp on what the problem is from the debugging that you've already done. Do you have a suggested patch to fix the problem?
Marking this bug as invalid, since the two-login problem with Slashdot is Slashdot's problem. The other portion of the cookie bug has been reincarnated in bug 46989. And Morse: I have no idea of how to fix this thing. I only know that the cookie service is created too late; I have no idea why this is happening, though.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
Summary: Cookie service created AFTER 1st HTTP request if component.reg missing (linux only) → Weird cookie behavior on Slashdot
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.