Bugzilla constantly requires re-login

Hi All,

I have been trying to log a bug at bugzilla.libsdl.org but every time I
navigate around I have to re-enter my username and password. I have
cookies enabled and no other restrictive settings as far as I know.

Does anyone know what the problem could be?

Thanks very much,

Andy

One of qualcomm’s websites does this to me at work.
They use HTTP auth (so I get a pop-up window when I go to a page,
and get an error 403 or some-such if I hit cancel or enter the wrong
username/password).

I ask Mozilla to store the password… which it does. Thing is, the
’title’ for the login AUTH seems to be unique each time, for whatever
retarded reason, so my Moz password manager is full of the same stuff
over and over again, and it never auto-fills for me, since it thinks I’m
being asked for a password for something different.

Dunno if Bugzilla is doing the same, but figured I’d take my opportunity
to rant about the idiocies of Qualcomm. :)On Fri, Jan 12, 2007 at 10:04:27AM +0000, Andy Balaam wrote:

I have been trying to log a bug at bugzilla.libsdl.org but every time I
navigate around I have to re-enter my username and password. I have
cookies enabled and no other restrictive settings as far as I know.

Does anyone know what the problem could be?


-bill!
bill at newbreedsoftware.com
http://www.newbreedsoftware.com/

Hello !

I have been trying to log a bug at bugzilla.libsdl.org but every time I
navigate around I have to re-enter my username and password. I have
cookies enabled and no other restrictive settings as far as I know.

The same problem here.

CU

I have been trying to log a bug at bugzilla.libsdl.org but every time I
navigate around I have to re-enter my username and password. I have
cookies enabled and no other restrictive settings as far as I know.

Does anyone know what the problem could be?

Probably a bug in our configuration, I’ll look into it.

–ryan.

I have been trying to log a bug at bugzilla.libsdl.org but every time I
navigate around I have to re-enter my username and password. I have
cookies enabled and no other restrictive settings as far as I know.

Does anyone know what the problem could be?

Probably a bug in our configuration, I’ll look into it.

The best I’ve come up with is that moving from an http:// to an https://
URL causes your login cookie to get hosed. I think we force you to an
SSL connection when you need to log in.

–ryan.