hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Shcheklein (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPCLIENT-1640) Failed to parse cookie max-age attribute
Date Tue, 14 Apr 2015 22:06:58 GMT
Ivan Shcheklein created HTTPCLIENT-1640:

             Summary: Failed to parse cookie max-age attribute 
                 Key: HTTPCLIENT-1640
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1640
             Project: HttpComponents HttpClient
          Issue Type: Bug
          Components: HttpCookie
    Affects Versions: 4.4.1
            Reporter: Ivan Shcheklein

[Url to reproduce|http://bit.ly/1Oy8Eho] (need to follow redirects)

{{2015:04:15 00:47:10,467 [WARN ] org.apache.http.client.protocol.ResponseProcessCookies -
Invalid cookie header: "Set-Cookie: sr=true; path=/; expires=Tue, 14 Apr 2015 21:36:16 GMT;
max-age=30;". Invalid 'expires' attribute: 30}}

{{RFC6265CookieSpecBase}} tries to parse max-age value with {{LaxExpiresHandler}} that expects
value to be in a cookie-date format, as far I understand. Meanwhile [RFC6265 states|http://tools.ietf.org/html/rfc6265#page-20]:

"... Append an attribute to the cookie-attribute-list with an attribute-name of Max-Age and
an attribute-value of expiry-time..."

[It seems|http://tools.ietf.org/html/rfc6265#page-19] it should just ignore invalid expires
value anyway:

"...If the attribute-value failed to parse as a cookie date, ignore the

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message