Cookie.setPath Inconsistent with RFC 2109

Question

My reading indicates that Java EE imposes an additional restriction beyond that in RFC 2109 on setting Cookies. That does not make policy sense. Am I interpreting the specification correctly? If so, should the Java EE part be changed?
From Java EE 5 documentation for Cookie.setPath(.)
bq. {color:#999999} \\ public void setPath(String uri) \\ Specifies a path for the cookie to which the client should return the cookie. \\ The cookie is visible to all the pages in the directory you specify, and all the pages in that directory's subdirectories.{color} A cookie's path must include the servlet that set the cookie, for example, /catalog, {color:#999999}which makes the cookie visible to all directories on the server under /catalog.{color} \\ Consult RFC 2109 (available on the Internet) for more information on setting path names for cookies.
From RFC 2109: http://www.ietf.org/rfc/rfc2109.txt
bq. 4.3.2 Rejecting Cookies \\ To prevent possible security or privacy violations, a user agent \\ rejects a cookie (shall not store its information) if any of the \\ following is true: \\ * The value for the Path attribute is not a prefix of the request- \\ URI. \\ {color:#999999} \\ * The value for the Domain attribute contains no embedded dots or \\ does not start with a dot. \\ * The value for the request-host does not domain-match the Domain \\ attribute. \\ * The request-host is a FQDN (not IP address) and has the form HD, \\ where D is the value of the Domain attribute, and H is a string \\ that contains one or more dots. \\ {color}

Answer 1

You can provide feedback to Apple here >  Apple - Safari - Feedback