|
Quick Lists
|
|
Bug ID:
|
6641315
|
|
Votes
|
0
|
|
Synopsis
|
HttpCookie a bit too strict when parsing expiration date
|
|
Category
|
java:classes_net
|
|
Reported Against
|
|
|
Release Fixed
|
|
|
State
|
11-Closed, duplicate of 6644726,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
|
|
Submit Date
|
13-DEC-2007
|
|
Description
|
HttpCookie expects the format to be "EEE',' dd-MMM-yyyy HH:mm:ss 'GMT'" (as specified in the proper RFC)
e.g.:
- FPS=ds;expires=Wed, 19-Aug-2015 16:00:00 GMT;path=/;domain=www.yahoo.com
But some sites have a slightly different formats:
- FPHH=2;expires=Sun, customer Dec 2007 13:23:04 GMT;path=/;domain=www.yahoo.com
- FPCK=R0WC0eQA;expires=Fri Nov 23 2007 14:23:03 GMT+0100 (CET);path=/;domain=www.yahoo.com
A less strict date parsing is necessary for a wider compatibility.
Posted Date : 2007-12-13 10:43:45.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
See description. A few more date formats should be accepted.
Will fix as soon as possible.
Posted Date : 2007-12-13 10:58:42.0
This has been included in the cookie management issues bucket.
See CR 6644726.
Closing as duplicate.
Posted Date : 2008-04-08 12:40:04.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
