Description of Problem: The Bugzilla login mechanism doesn't work through a Squid web-proxy (and possibly others). Tested with IE 5.5, NS 4.77, KDE 2.1. How Reproducible: Always Steps to Reproduce: 1. Set the web browser to use the proxy. 2. Login in to bugzilla. 3. Go to a new bugzilla page. Actual Results: Bugzilla says "Not logged in, please log in" Expected Results: Login should be remembered. Additional Information: The option of bypassing the proxy is not available at most security consious sites.
It works for me. Is your proxy set to squash cookies?
I don't think so. I'm prompted if I want to accept cookies while viewing several sites. However, I'm not prompted when logging in to bugzilla, so I expect that the problem somehow is related to cookie handling. By the way, is there a reason for using cookies instead of WWW-Authenticate?
WWW-Authenticate uses a directory based form of authentification and also uses a simple flat file for password/username pairs. Bugzilla uses a complex database structure for holding user information and currently has to use cookies for this to work. New, more efficient forms, of authentification are being worked on.
Junkbuster was eating my bugzilla cookies - added redhat.com to /etc/junkbuster/cookiefile and things are better. Running standard Enigma junkbuster and squid RPMS with junkbuster forwarding to squid.
Can this really be proxy related? Surely https doesn't go via proxy? At any rate, I experience the "login not remembered" problem if I access using netscape 6, but not if I access using lynx, whether or not I enable proxies in netscape or lynx. (fails either way with netscape, works both ways with lynx). Netscape is set to allow cookies, and if I get it to prompt, I get told that the site wants to modify an existing cookie (twice) so it must have set them.
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to this version. Any bugs against the older versions will need to be verified that they are still bugs. This will help me also to sort them better.
Setting configuration problem. Works for me from many different locations.