On Monday 11 November 2002 01:51 am, you wrote: > Something interesting, I spotted the cookie debug options in mon.cgi and > uncommented them. The strings that appear at the top of the webpage are: > cookie value is (never changes) > encrypt password is (never changes) > username is "" > decrypt password is "" > > The last two have the correct values in them when I log in, but *only* > for the page following me logging in. Some more fiddling shows that no > matter what user/pass I type in, it accepts it for the first page, but > then forgets it....WTF??
Since cookie value, username and password are blank, as read by mon.cgi from the cookie contents, TF is, you have either a problem with: 1) your browser not accepting the cookie properly 2) your browser expiring the cookie early 3) your browser somehow not presenting the cookie back to mon.cgi 4) mon.cgi somehow not being able to parse the cookie I would doubt #4 is the case, since mon.cgi uses very standard cookie parsing as provided by CGI.pm. That leaves 1,2, and 3, all of which could have several possible causes. So, try a couple of different browsers on a couple of different machines. If they all failed, I'd be very surprised. Every piece of evidence so far points to a client-side problem. cheers, andrew _______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
