First regarding the cookie with no name, read Re^4: Cookie->fetch problem near the bottom after "and note that if i run". you put it there once when you passed back a cookie without setting the name to CGISESSID, and you may keep doing it too.
clicked the button for the script and it showed no cookies.
you are not clear but i think you are saying the the script showed no cookies returned. I think this is a mismatch with your path/domain and maybe secure that the cookie should be returned to. look closely at the http:://some.domain.com/ file you are going to, compare that to the address the cookie is stored under. i have cookies stored for both m.staples.com and staples.com. The next part is the path. if the cookie says the path is / then it will be sent back to the server for any page, but of the cookie says the path is /cgi-bin it will only be sent back if you are going to http:://some.domain.com/cgi-bin pages. you were setting the domain when you returned the cookie, if you didnt get it right when you set it it wont get returned. Another thing you were setting wad the secure option. cookies with the secure option only get returned if you have a secure (https/SSL connection. if you are now going to a plain http: address or the SSL negotiation is failing the browser will not return the cookie.
This page https://www.nczonline.net/blog/2009/05/05/http-cookies-explained/ seems to explain things pretty good.
In reply to Re^7: Cookie->fetch problem
by huck
in thread Cookie->fetch problem
by tultalk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |