If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Cookie expiration date doesn't used if host contains an ip address and not an hostname.

UNCONFIRMED
Unassigned

Status

Mozilla Labs
Prism
UNCONFIRMED
8 years ago
8 years ago

People

(Reporter: contact, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.1.5) Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091109 Prism/1.0b2

When you set up a cookie, with an expiration date (other than end of session), and if the 'host' is filled by an ip address, the 'expires' field become 'end of session' and not the expiration date you've settled up.

I've add an alias to this ip address in my /etc/hosts, and then the cookie was ok.

Reproducible: Always

Steps to Reproduce:
1. build an app that send cookie with an expiration date (example : 7 days)
2. go o this app using her ip address
3. check the cookie content in prism
Actual Results:  
The cookie expiration date was incorrect : 'end of session' instead of the date.

Expected Results:  
The cookie should have to correct expiration date.
(Reporter)

Comment 1

8 years ago
I don't know why, but with the same version (Prism 1.0b2) on another computer with a fresh installation of Kubuntu 9.10, the bug isn't here.

I guess it was a distribution-specific problem.

Just in case : the problem was encountered on Linux i686 with an 'old'/upgraded version of Kubuntu 9.10, and when it disappeared on the fresh installation it was with Linux x86_64.
You need to log in before you can comment on or make changes to this bug.