Cookie testing prevents login

[ryan]

 http://wordpress.org/support/topic/135598?replies=11

Some are having login problems that are fixed when the cookie testing code is removed. See [6009].

Let's gather some information. Browser version, http server version, firefox extensions, anti-virus/firewall software, etc.

Some notes:

Original reporter on wp-testers has 3 blogs on same domain on same host (2 work - 1 doesn't)

There is a limit on the number of cookies per domain based on RFC2109:

6.3 Implementation Limits

Practical user agent implementations have limits on the number and size of cookies that they can store. In general, user agents' cookie support should have no fixed limits. They should strive to store as many frequently-used cookies as possible. Furthermore, general-use user agents should provide each of the following minimum capabilities individually, although not necessarily simultaneously:

• at least 300 cookies

• at least 4096 bytes per cookie (as measured by the size of the characters that comprise the cookie non-terminal in the syntax description of the Set-Cookie header)

• at least 20 cookies per unique host or domain name

User agents created for specific purposes or for limited-capacity devices should provide at least 20 cookies of 4096 bytes, to ensure that the user can interact with a session-based origin server.

The information in a Set-Cookie response header must be retained in its entirety. If for some reason there is inadequate space to store the cookie, it must be discarded, not truncated.

Applications should use as few and as small cookies as possible, and they should cope gracefully with the loss of a cookie.

Note also - setcookie will fail (possibly silently) if the headers are already sent according to  http://uk.php.net/setcookie

Set TEST_COOKIE for SITECOOKIEPATH

Maybe we need to set the cookie with SITECOOKIEPATH in addition to COOKIEPATH.

(In [6167]) Set TEST_COOKIE for SITECOOKIEPATH. see #5076

(In [6168]) Set TEST_COOKIE for SITECOOKIEPATH. see #5076

Replying to ryan:

Maybe we need to set the cookie with SITECOOKIEPATH in addition to COOKIEPATH.

I guess maybe I should have a test install in a subdirectory and maybe I would have caught this one then :-(