| Summary: | HttpFields.addSetCookie adds Expires HTTP header using cookie date format instead of http date format | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | karlgold |
| Component: | server | Assignee: | Greg Wilkins <gregw> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jetty-inbox, jorgen.rydenius |
| Version: | unspecified | ||
| Target Milestone: | 7.2.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
karlgold
Do not apply the patch proposed above since that would cause bug #338364 to return. Both formats of 1 Jan 1970 are required since they are used in two different cases, the HTTP Expires header and the Expire part of Netscape style cookies. The two uses should have different formats, changing the definition of __01Jan1970 back and forth is not the solution. See my original patch of bug #338364 for a working alternative. This is bug #338364? I think you must mean #304698 or #304658 Fixed in jetty-7 r3162 and jetty-6 r6570 by reverting to the patch proposed in 304658. But also found an issue where the expires header was not being set if other cancelled fields existed. Also fixed. thanks as above Sorry about the mixup of bug numbers. Bug #338364 should be replaced by bug #304658 in my previous comment. But I can see you figured out that yourself. Thank you. |