in reply to Re: Two CGI.pm problems
in thread Two CGI.pm problems

>The IE behavior should be considered a feature.

I believe this answer stems from a complete misunderstanding of the original poster's question.

Doesn't "session-only" mean "until the browser is quit?"

The cookie is not saved until the browser is quit, according to the OP's account. It's lost, in IE, right away, so, not a feature.

I know there are bugs in some versions of IE which require the path to be set, but I don't think that's common-- Mac version 5 only?

Short answer: show us your code, and check out the exact details of the cookie using a browser which allows you do do that.

Does your "log-in successful" page actually check that a cookie has been set? Or does it just assume that it's been set? What are the conditions you check in order to return "log-in successful"?


($_='kkvvttuubbooppuuiiffssqqffssmmiibbddllffss')
=~y~b-v~a-z~s; print

Replies are listed 'Best First'.
Re^3: Two CGI.pm problems
by ido50 (Scribe) on Jun 08, 2004 at 19:03 UTC
    First I should say that when I changed the cookie expiration time from 30 minuts to 1 day, it was created.
    And yes, I assumed the cookie was created. I'll fix that and see what happenes, but I guess that won't be neccessary (For the sake of the matter, not the sake of the program), 'cause I use Mozilla's developer plugin which displays information on all cookies the page uses. When trying to login with IE (Without the 'remember me'), it does not find a cookie, so it is definitely not created.
    Anyway, it's pretty interesting that when giving an expiration time of a number of days the cookie is created, but when giving an expiration time of minuts or hours it's not.

    -------------------------
    Live fat, die young
[reply]

In Section Seekers of Perl Wisdom