From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3) Gecko/20010801 BuildID: 2001080110 URL shown with error page: https://jsource.j2.com/main.asp?page= Error page displays: Cookies object error 'ASP 0200 : 80004005' Out of Range 'Expires' attribute /main.asp, line 208 The date given for 'Expires' precedes Jan 1, 1980 or excedes Jan 19, 2038, 3:14:07 GMT. Reproducible: Always Steps to Reproduce: 1. Go to URL 2. Enter phone number and code 3. Press Enter - error message appears after 10-20 secs Actual Results: See description Expected Results: Log in to site Obviously it will be hard to test unless you have an account! If there is anything you want me to do to test it, let me know.
Please try to find the offending cookie in your cookies.txt file (anything with mentiones j2.com in the first column) and post it here. Although it isn't exactly an error if you have a cookie which is before 1980 (I have several in 1971) or after 2038. The server shouldn't give an error for this.
There are no j2 ones in cookies.txt - I checked in the cookie manager and there are several j2.com and jsource.com (also relates to this site) SESSION cookies, if that helps. Perhaps I should raise it with j2.com?
This certainly sounds like a server issue. The message you are reporting is coming from the server. Have you tried this with other browsers -- namely netscape 4.x and any flavor IE. If they give the same problem then there's no doubt that it's a server issue.
It works fine with IE5.5, that is what I normally use but I will e-mail the site and ask if they are aware of the issue.
Unable to fix unless I can test this out and, as the reporter commented, this requires that I have an account. So I'm going to have to close this out as WONT-FIX. If reporter wants this investigated further, he'll have to e-mail me privately and give me his username and password so I can test it out.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
QA Contact: tever → benc
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.