Closed Bug 140464 Opened 22 years ago Closed 22 years ago

Cookies expire at end of session if Date header is missing

Categories

(Core :: Networking: Cookies, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.0

People

(Reporter: marc.loiselle, Assigned: morse)

References

()

Details

(Whiteboard: [adt2 rtm],custrtm-)

Attachments

(1 file)

Going to thig url
http://www.vcitysoftware.com:8081/examples/servlet/CookieExample?cookiename=test&cookievalue=value

should set a cookie that expires in 60 minutes.  It does not.  According to the
Cookie Manager, the cookie expires at the end of the session.

This is happening because the webserver (Tomcat 3.2.3) does not send a Date
header in the response.

An empty server_date is being passed to COOKIE_SetCookieStringFromHttp instead
of null due to a recent change in nsCookieHTTPNotify.cpp.

I will attach a patch that fixes the problem.
Forgot to mention the buildId.  It is 2002042403 - Win2K.  The problem happens
with 1.0RC as well.  The problem does not occur with 0.9.9.
Comment on attachment 81238 [details] [diff] [review]
Patch that fixes the problem

r=morse
Attachment #81238 - Flags: review+
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: approval, patch
OS: Windows 2000 → All
Hardware: PC → All
Comment on attachment 81238 [details] [diff] [review]
Patch that fixes the problem

sr=darin
Attachment #81238 - Flags: superreview+
Keywords: adt1.0.0
Stephen, 

Can you check in my patch to the trunk?

How do I get my patch approved to go into the 1.0 branch?
Gagan, steve is on vacation, can you check this in?
Keywords: nsbeta1
Whiteboard: [Need Impact from Nav team]
Keywords: mozilla1.0
no can do this week (in dulles) try dougt
Before it can be checked in, it needs both a= and adt1.0.0+.

Peter - Any word from Nav triage oin whether this is needed for RC2 or not?
Is this happening on any top sites, or with any popular servers?
The patch just simply corrects a regression.  The patch has minimal risk.
That's not what I asked.
Peter, I don't know if it is happening on top sites.  I just know that it is a
bug and it needs to be fixed since it worked before.  The problem also occurs if
the Date field is after the Set-Cookie field in the header.  This is a very
simple fix.
We have a fix, I just need to determine if it has high enough impact to require
taking the fix for beta.  So far, we are unaware of any impact to target users.
Comment on attachment 81238 [details] [diff] [review]
Patch that fixes the problem

a=asa (on behalf of drivers) for checkin to the 1.0 branch. We're tight on time
so please land this ASAP.
Attachment #81238 - Flags: approval+
Nav triage team: nsbeta1+, adt2 rtm
Keywords: nsbeta1nsbeta1+
Whiteboard: [Need Impact from Nav team] → [adt2 rtm]
Why has the patch not been checked into the trunk or the 1.0 branch?  There are
approvals for both.
no, it doesn't.  a= is outdated, and there is no ADT approval.
I thought that the a= is not required for the trunk.  Also, I didn't know that
a's expired.  I am getting frustrated by the process.  Patch should have checked
in to the trunk on Apr 30.  I understand that the process for patching the
branch is more difficult but to delay the check in for the trunk seems odd.
You're right that a= is needed only on the branch, but nobody is purposely
delaying checkin to the trunk.  AFAIK, mozilla.org gives a= that is good for 3
days only.  I understand your frustration, but that is not my process, though I
do support it.  Steve Morse is on vacation until Monday, and my other engineers
are fully booked on work that is needed for our beta, but if you can get someone
else to check this in on the trunk for you, then go right ahead.
Checked in on trunk.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
fixed
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
adding adt1.0.0+.  Please get drivers approval since it's been more than 3 days
and then check into the 1.0 branch.
Keywords: adt1.0.0adt1.0.0+
valeski just reapproved for drivers.  checked in on branch.
Keywords: fixed1.0.0
verified trunk and branch, 05/28/02 builds winNT4, linux rh6, mac osX
Status: RESOLVED → VERIFIED
Whiteboard: [adt2 rtm] → [adt2 rtm],custrtm-
Keywords: verified1.0.0
Keywords: fixed1.0.0
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: