HttpHeaders should be tolerant with bad date-aware headers as it said in the RFC 2616 [SPR-10648]

[spring-projects-issues]

Artem Bilan opened SPR-10648 and commented

See the Expires header description in the RFC.
Now if the value of similar header is not valid HttpHeaders throws IllegalArgumentException.
IMO it should return -1 as in case header is null.
In additions see the linked issue.

We'll be glad to hear any thoughts, why HttpHeaders works now such way?

---

Affects: 3.2.3

Reference URL: http://tools.ietf.org/html/rfc2616#page-127

Issue Links:

• INT-3063 HTTP gateway response fails with non-standard expires header

Referenced from: commits 9245fff, 0f71da5

[spring-projects-issues]

Rossen Stoyanchev commented

Arjen Poutsma, any objections? The RFC does say "HTTP/1.1 clients and caches MUST treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired")."

[spring-projects-issues]

Arjen Poutsma commented

No objections.