Bug 7906
Summary: | Bad Cookie Expiration Dates | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | davek |
Component: | Bugzilla General | Assignee: | David Lawrence <dkl> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1rC | CC: | davek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-01-24 18:59:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
davek
1999-12-20 18:03:02 UTC
This does not seem to be causing any trouble on our end. The reasoning that the date is set as such is that it automatically becomes an invalid cookie upon bein set so when you relogin it will set the cookies to a valid state with 2029 as the expiration year. |