The browser cannot ask the server because the cookie is written.

Writing a cookie causes the browser to fail to ask the server's browser to repeatedly refresh the request for a php page (this page will rewrite the cookie once it is accessed) and refresh it to a certain extent (about 10-20 times) the server cannot be accessed. if the server cannot be accessed again after the cookie is cleared, the browser cannot ask the server.
The browser constantly refreshes the request for a php page (this page will write a cookie again when accessed). if it is refreshed to a certain extent (about 10-20 times), it will not be able to access the server, you need to clear the cookie before you can access it again.

When the access fails, the Request headers is as follows:
GET http: // XXX/test. php HTTP/1.1
Accept: text/html, application/xhtml + xml, application/xml; q = 0.9, */*; q = 0.8
Cache-Control: max-age = 0
User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36

When the access fails, the request cannot be sent. it seems that it is very hard to read the local cookie, that is, it cannot be read.
Cookie server share:
------ Solution --------------------
Restrictions on the server
------ Solution --------------------
Cookie verification problems
Restricted page verification cookie problems, so jump to the login page
Log on to the page to determine whether the cookie exists and jump to the restricted page

After the browser continuously receives the jump command, it determines that the server is not connected due to a problem