RFC 6265, "HTTP State Management Mechanism", April 2011Source of RFC: httpstate (app)
Errata ID: 4043
Publication Format(s) : TEXT
Reported By: Pierre Lepropre
Date Reported: 2014-07-06
Rejected by: Barry Leiba
Date Rejected: 2014-07-12
Section 5.1.4 says:
The user agent MUST use an algorithm equivalent to the following algorithm to compute the default-path of a cookie:
It should say:
The user agent MUST use an algorithm equivalent to the following algorithm to compute the default value for a cookie-path (and thereby matching the server-side semantics as defined in 184.108.40.206):
The term "default-path" is not formally defined before and is quite misleading for the reader
A. going through the section 5.1.4 as it's only used there once and not again
until section 5.2.4 (once again) and 5.3 (once again).
B. not being a native English speaker
Furthermore, the true meaning of the "default-path" only appears sometime after at section 5.2.4 where it's finally bound altogether. Therefore, my personal recommendation would be to also replace the other occurrences of the "default-path" terms by "default cookie-path"
This report is actually an enhancement request. The discussion of this report on the http-state mailing list should be reviewed if the document is ever revised.