Doc #52916 [Opn->Asn]: Reference to old RFC version

Edit report at http://bugs.php.net/bug.php?id=52916&edit=1 ID: 52916 Updated by: aharvey@php.net Reported by: ds11 at o2 dot pl Summary: Reference to old RFC version -Status: Open +Status: Assigned Type: Documentation Problem Package: Documentation problem Operating System: - PHP Version: Irrelevant -Assigned To: +Assigned To: aharvey Block user comment: N New Comment: I suspect the original spec is being referred to because it's considerably more readable than the RFC, rather than because it's considered authoritative. It would probably be best to relegate the links to the Netscape spec to the See Also section (with an appropriate name) and either find another resource to fall back on or roll a description of tail matching into the setcookie() page proper. Previous Comments: ------------------------------------------------------------------------ [2010-09-23 17:51:45] ds11 at o2 dot pl Description: ------------ I noticed that on this page: http://php.net/manual/en/function.setcookie.php in section "Parameters" -> "domain" you refer to an old version of a set-cookie spec. However it was never approved for common use. You should refer to: http://www.ietf.org/rfc/rfc2109.txt This is especially important for the domain because your reference says: " Only hosts within the specified domain can set a cookie for a domain and domains must have at least two (2) or three (3) periods in them to prevent domains of the form: ".com", ".edu", and "va.us". Any domain that fails within one of the seven special top level domains listed below only require two periods. Any other domain requires at least three. The seven special top level domains are: "COM", "EDU", "NET", "ORG", "GOV", "MIL", and "INT". " but ultimately the limitation was dropped (see my link), e.g. you can use .my.tv as a domain. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=52916&edit=1