JDK-6641315 : HttpCookie a bit too strict when parsing expiration date
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 6
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2007-12-13
- Updated: 2010-04-02
- Resolved: 2008-04-08
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
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, 02 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.
Comments
|